Make some float methods unstable const fn
#130568
Open
+299
−148
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some float methods are now
const fn
under theconst_float_methods
feature gate (exceptf16
andf128
versions, which I placed underf16
andf128
feature gates respectively).In order to support
min
/max
, the implementation of some intrinsics had to be moved from Miri to rustc_const_eval (cc @RalfJung).If this is accepted, a tracking issue should be created (for now I set
issue = "none"
).r? libs-api