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
Is there any significance in the choice made between dots and colons in section names and also between representing underscores as-is and replacing them with dots? And does it make sense to come up with a consistent system, going forward? (I think too many external resources use the names as anchors to consider changing the existing ones)
grep tells me there are 38 section names with the :: (from [ios::failure] to [string::op>=]) and 1763 section names with dots, with no pattern to the colons other than clustering: it seems that colons shouldn't be used going forward.
Same for section names that use underscores directly (85 hits) vs the ones that replace each underscore with a dot (can't count with grep, examples include [memory.resource.monotonic.buffer] or [string.view]) -- this is less clear.
The text was updated successfully, but these errors were encountered:
All this is wildly inconsistent. But I doubt we'll ever change any of the existing stable names. As far as new sections are concerned, I believe the working groups are aware of the need to pay attention to the stable section naming.
Is there any significance in the choice made between dots and colons in section names and also between representing underscores as-is and replacing them with dots? And does it make sense to come up with a consistent system, going forward? (I think too many external resources use the names as anchors to consider changing the existing ones)
grep tells me there are 38 section names with the
::
(from[ios::failure]
to[string::op>=]
) and 1763 section names with dots, with no pattern to the colons other than clustering: it seems that colons shouldn't be used going forward.Same for section names that use underscores directly (85 hits) vs the ones that replace each underscore with a dot (can't count with grep, examples include
[memory.resource.monotonic.buffer]
or[string.view]
) -- this is less clear.The text was updated successfully, but these errors were encountered: