RustCrypto / RustCrypto/crypto-bigint
auto-godbolt analysis / snapshot record & compare
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 309
- Forks
- 95
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Description
Would it be worthwhile to collect auto-godbolt spitout for every PR and see readily how the asm changes between platforms associated to PR ?
It could maybe even memorize problematic patterns which then needs to be. maybe ticked somehow off
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by clarifying what auto-godbolt output should be collected for each pull request and which platform differences must be compared. Define how snapshots and problematic patterns would be recorded and reviewed; done means the workflow and comparison scope are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100