Contemplate rustc_apfloat for platform consistent floats #44
Labels
No labels
Area/build-packaging
Area/evaluator
Area/flakes
Area/profiles
Area/remote-builds
Area/repl
Area/store
bug
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#44
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Nix regrettably has floats, which can be used to implement ray tracers and other inadvisable things. We would rather it didn't, but let's make them consistent.
I'm a bit unsure how strongly this is needed; IEEE floats should be bit-identical for the base (divide, add, subtract, multiply) operations. It might be good to have either way, though.
(I also like how mentioning
)
rustc_apfloat
immediately divulges who you got this idea from, rather than mentioning the upstream llvm APFloat