Investigate fearless_simd crate
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- cryptography, performance
Research direction
Start by reviewing the fearless_simd crate documentation and source, including its quality, tests, maintenance prospects, and license. Then inspect crypto/mldsa/src/polynomial.rs and prototype SIMD vectorization there, measuring the result. Done means a documented dependency recommendation, prototype benchmark results, and a conclusion about cargo feature and build implications.
Written by the indexing model from the issue text.
Description
Background
We will eventually have to look at SIMD to speed up bit of code that are performing the same computation many times in parallel.
The crate:
https://docs.rs/fearless_simd/latest/fearless_simd/
looks promising.
Task
- Perform a code review of the
fearless_simdcrate and form an opinion about whether this is a thing we would want as a core dependency. Some questions to think about:- Does it feel like it meets the same quality standards as bc-rust (code quality, readability, tests, etc).
- Do we feel that if we absolutely had to, we have the skills and bandwidth to hard-fork and take over maintenance of that crate?
- Is its license compatible with the above?
- Do a prototype. I would suggest that SIMD-vectorizing mldsa/polynomial.rs would give the most dramatic benchmark speedup of all the stuff that we've implemented so for.
- Think about build implications: would this need a new cargo feature, or could we safely leave it always-on?
- Dominant language
- Rust
- Stars
- 25
- Forks
- 18
- Avg merge
- 14d 10h
- Merged PRs (30d)
- 5
Getting set up
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.
More from bcgit/bc-rust
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bcgit/bc-rust#161 · 1 reaction ·
Maintainers usually reply within 2 days
-
good first issue refactor
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bcgit/bc-rust#163 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 2 days
-
documentation good first issue refactor
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 2 days
Similar issues
-
discover: `sudo RTK_DISABLED=$VAR …` is not detected as a bypass when `sudo` is a transparent prefixOpenarea:cli bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
skill:code-review
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
component:sight
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
agentic-os-org/ANOLISA#4115 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rivet-dev/rivet#5819 · 1 comment ·
Maintainers usually reply within 1 day
-
A-io-database bug needs triage python
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day