Consider using an embedded libm
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Monday Dec 02, 2013 at 20:41 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/10774
This issue was labelled with: I-wishlist in the Rust repository
For performance and consistency reasons, we might want to bundle our own libm. It further reduces our dependency on system libraries, opens the potential for LTO, and gives us something we can control and define.
A good candidate is openlibm, which has a long history.
See https://github.com/mozilla/rust/issues/5702, https://github.com/mozilla/rust/issues/1222
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
No files or tests are named. Start by reading the earlier discussion in rust-lang/rust#10774 and the linked mozilla/rust issues, then review openlibm's scope. Done would require a decided design for whether and how Rust should bundle an embedded libm.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100