Date: Tue, 23 Jun 2026 12:24:23 -0400
normal_max and normal_lowest are not available with numeric_limits. I think
those should be highlighted too. Since max and lowest correspond to T_MAX and
-T_MAX respectively instead of T_NORM_MAX and -T_NORM_MAX respectively.
On Tue, Jun 23, 2026 at 11:49 AM Jan Schultke via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> https://isocpp.org/files/papers/D4285R0.html
>
> Hi, I've brought up the idea of having a more powerful replacement for std::numeric_limits a while ago. I've now gotten around to drafting up a paper. Let me know what you think of the direction.
>
> In a nutshell, there is a lot of information that std::numeric_limits doesn't provide, and we cannot fix that because it would break users' specializations. Having more floating-point information would enable users to implement a lot more things portably using the information they get from the standard library.
>
>
> Jan
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
those should be highlighted too. Since max and lowest correspond to T_MAX and
-T_MAX respectively instead of T_NORM_MAX and -T_NORM_MAX respectively.
On Tue, Jun 23, 2026 at 11:49 AM Jan Schultke via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> https://isocpp.org/files/papers/D4285R0.html
>
> Hi, I've brought up the idea of having a more powerful replacement for std::numeric_limits a while ago. I've now gotten around to drafting up a paper. Let me know what you think of the direction.
>
> In a nutshell, there is a lot of information that std::numeric_limits doesn't provide, and we cannot fix that because it would break users' specializations. Having more floating-point information would enable users to implement a lot more things portably using the information they get from the standard library.
>
>
> Jan
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
Received on 2026-06-23 16:23:59
