-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Fix incorrect use of MaybeUninit::assume_init_mut in flt2dec #76092
Comments
Besides the float code, there's also the |
Could we rename it to validity of Regarding the issue at hand, obviously only Doing so is not that bad as when I attempted to tackle #66174, since by now we have initiatives such as the one I suggested there having been implemented in a library crate, using a library version of out references, and we also have the aforementioned RFC getting some progress. So this time, letting the FIXME without fixing it yet is not just a "useless procrastination of the problem", it is a meaningful "wait for the required language feature", I'd say 🙂 |
The issue is not really specific to floats, it is tight to whether references are allowed to refer to uninitialized data. So this is basically the rustc side of (a part of) rust-lang/unsafe-code-guidelines#77. |
Agreed for the |
Creating this issue to track this FIXME note in float formatting:
The issue being mentioned when the fixme was closed without addressing this concern, and the new tracking issue doesn't raise it, so created this so that we can discuss it here and link it to the tracking issue
cc @RalfJung
The text was updated successfully, but these errors were encountered: