Implement fmt traits for floating-point types
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Currently f32 and f64 do not implement many of the fmt traits:
fmt::Binary: does.to_bits()and prints the integer as binaryfmt::Octal: does.to_bits()and prints the integer as octalfmt::LowerHex: equivalent toprintf("%a")[0]fmt::UpperHex: equivalent toprintf("%A")[0]
That is pretty annoying when working with floating point numbers. Methods that would allow to format independent parts of the representation like the mantissa would also help.
cc @cuviper
[0]: to obtain the hex representaiton of the float as an integer one can just use .to_bits().
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 reviewing the requested f32 and f64 implementations for fmt::Binary, fmt::Octal, fmt::LowerHex, and fmt::UpperHex, including the stated to_bits() and printf("%a") comparisons. No source file or test is identified; done would require a resolved design and corresponding Rust RFC or implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100