You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WG21 merged P1754R1 "Rename concepts to standard_case for C++20" into the working draft as LWG Motion 11 in 2019 Cologne. That proposal contains editorial instruction to rename what was the DefaultConstructible concept:
IF LWG3151 ACCEPTED:
default_initializable
ELSE
default_constructible
Notably LWG 3151 "ConvertibleTo rejects conversions from array and function types" is not the intended issue number here - I misremembered the issue number - [LWG 3149 "DefaultConstructible should require default initialization"] is. It was made clear during discussion in LEWG that 3149 would change the concept to require default-initialization to be valid rather than value-initialization which the is_default_constructible trait requires. LEWG agreed that it would be confusing to have a trait and concept with very similar names yet slightly different meanings, and approved the proposed renaming.
The proposed resolution of LWG 3149 was approved by LWG in Cologne as well, but - per LWG procedure - that means the issue was made "Ready" but not moved until Belfast. WG21 voted to merge the resolution of LWG 3149 in Belfast.
Is this sufficient evidence to indicate that WG21 desires that the default_constructible concept be editorially renamed to default_initializable?
The text was updated successfully, but these errors were encountered:
WG21 merged P1754R1 "Rename concepts to standard_case for C++20" into the working draft as LWG Motion 11 in 2019 Cologne. That proposal contains editorial instruction to rename what was the
DefaultConstructible
concept:Notably LWG 3151 "
ConvertibleTo
rejects conversions from array and function types" is not the intended issue number here - I misremembered the issue number - [LWG 3149 "DefaultConstructible
should require default initialization"] is. It was made clear during discussion in LEWG that 3149 would change the concept to require default-initialization to be valid rather than value-initialization which theis_default_constructible
trait requires. LEWG agreed that it would be confusing to have a trait and concept with very similar names yet slightly different meanings, and approved the proposed renaming.The proposed resolution of LWG 3149 was approved by LWG in Cologne as well, but - per LWG procedure - that means the issue was made "Ready" but not moved until Belfast. WG21 voted to merge the resolution of LWG 3149 in Belfast.
Is this sufficient evidence to indicate that WG21 desires that the
default_constructible
concept be editorially renamed todefault_initializable
?The text was updated successfully, but these errors were encountered: