This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of New status.
Section: 220.127.116.11 [constexpr.functions] Status: New Submitter: Great Britain Opened: 2017-02-03 Last modified: 2017-07-16
View all other issues in [constexpr.functions].
View all issues with New status.
Discussion:Addresses GB 38
Relax the prohibition on libraries adding constexpr; this was a constraint requested by library implementers when constexpr was new, and those same implementers now feel unduly constrained.
Proposed change: Rewrite the whole sub-clause to support libraries adding constexpr in a compatible manner, much like the freedom to add a noexcept specification.
[2017-02-20, Marshall adds wording]
The simplest change would be to strike the sentence "An implementation shall not […] explicitly required". However, people seem to want a definite permission here, so I have provided one.
[2017-07 Toronto Thurs Issue Prioritization]
This wording is relative to N4640.
Modify 18.104.22.168 [constexpr.functions] as indicated:
This International Standard explicitly requires that certain standard library functions are constexpr (7.1.5).
An implementation shall not declare any standard library function signature as constexpr except for those where it is explicitly required. Within any header that provides any non-defining declarations of constexpr functions or constructors an implementation shall provide corresponding definitions.