-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove f32 & f64 from MemDecoder/MemEncoder #109984
Conversation
a92833c
to
a9a680d
Compare
can you add a reference to this PR so that people can revert it if they need it later (which they probably don't but you never know)? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me
Sure thing; done. If you're here in the future: you might want to change how this works, because using LEB128 for floats is a poor choice -- even a simple float like Indeed, the only |
@bors r=Nilstrieb |
Remove f32 & f64 from MemDecoder/MemEncoder r? `@Nilstrieb` since they said (maybe joked) on discord that it's a bug if the compiler uses f32 anywhere 🙃
Remove f32 & f64 from MemDecoder/MemEncoder r? ``@Nilstrieb`` since they said (maybe joked) on discord that it's a bug if the compiler uses f32 anywhere 🙃
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#109395 (Fix issue when there are multiple candidates for edit_distance_with_substrings) - rust-lang#109755 (Implement support for `GeneratorWitnessMIR` in new solver) - rust-lang#109782 (Don't leave a comma at the start of argument list when removing arguments) - rust-lang#109977 (rustdoc: avoid including line numbers in Google SERP snippets) - rust-lang#109980 (Derive String's PartialEq implementation) - rust-lang#109984 (Remove f32 & f64 from MemDecoder/MemEncoder) - rust-lang#110004 (add `dont_check_failure_status` option in the compiler test) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
r? @Nilstrieb
since they said (maybe joked) on discord that it's a bug if the compiler uses f32 anywhere 🙃