View all comments

Feature gate: #![feature(float_minimum_maximum)]

This is the tracking issue for the f{32,64}::{min,max}imum functions.

It provide IEEE 754-2019 minimum and maximum functions to f32/f64.

Public API

impl f32 {
    pub const fn minimum(self, other: f32) -> f32;
    pub const fn maximum(self, other: f32) -> f32;
}

impl f64 {
    pub const fn minimum(self, other: f64) -> f64;
    pub const fn maximum(self, other: f64) -> f64;
}

Steps / History

• Implementation: Adds IEEE 754-2019 minimun and maximum functions for f32/f64 #91008
• Constified in Make some float methods unstable const fn #130568
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• Should the implementation be stabilized in it's current state (ie. without intrinsic: explanation and llvm issue) ?
  • Use intrinsics for {f16,f32,f64,f128}::{minimum,maximum} operations #140792
  • [aarch64] Cannot select: constant:i128<0> for llvm.maximum.f128 llvm/llvm-project#139380
  • [x86]: Cannot select: constant:i128<0> for llvm.maximum.f128 llvm/llvm-project#139381
  • [arm] Cannot select i32 = setcc 0x00000000, Constant:i64 llvm/llvm-project#140445
  • as of 2026-06-27, we are using the intrinsic for f16 and f32 but not for f64 and f128
• Should it be called like IEEE 754-2019 (minimum and maximum) or something else ? Tracking Issue for float_minimum_maximum #91079 (comment)
• Should the standard library have this function at all (we already have min/max) ?