diff options
| author | Daniel McNab <36049421+DJMcNab@users.noreply.github.com> | 2025-05-20 10:08:15 +0100 |
|---|---|---|
| committer | Daniel McNab <36049421+DJMcNab@users.noreply.github.com> | 2025-05-20 16:41:43 +0100 |
| commit | f6709bb6834818193efce3315f107744982d2d43 (patch) | |
| tree | b99bbe00d294a3c59c2216980141f8b99ccf0c7c /compiler/rustc_codegen_gcc/example/alloc_example.rs | |
| parent | a8e4c68dcb4dc1e48a0db294c5323cab0227fcb9 (diff) | |
| download | rust-f6709bb6834818193efce3315f107744982d2d43.tar.gz rust-f6709bb6834818193efce3315f107744982d2d43.zip | |
`core_float_math`: Move functions to `math` folder
When these functions were added in https://github.com/rust-lang/rust/pull/138087 It made a relatively common pattern for emulating these functions using an extension trait (which internally uses `libm`) much more fragile. If `core::f32` happened to be imported by the user (to access a constant, say), then that import in the module namespace would take precedence over `f32` in the type namespace for resolving these functions, running headfirst into the stability attribute. We ran into this in Color - https://github.com/linebender/color - and chose to release the remedial 0.3.1 and 0.2.4, to allow downstream crates to build on `docs.rs`. As these methods are perma-unstable, moving them into a new module should not have any long-term concerns, and ensures that this breakage doesn't adversely impact anyone else.
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions