We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Ideas from Belfast editorial session:
Move [format] to [strings], since it's essentially a fancy string constructor.
Move [stacktrace] to [diagnostics].
keep Utility types: pair, tuple, variant, optional, any, bitset under [utilities], but create a new grouping subclause called "data types".
Isn't "[charconv] Primitive numeric conversions" a good fit for Clause 26 "Numerics library"? I always searched there for it, at first.
Should [intseq] "Compile-time integer sequences" be a subclause of [utility] "Utility components" rather than a sibling?
Addressed with #5124
Activity
jensmaurer commentedon Nov 14, 2020
Move [format] to [strings], since it's essentially a fancy string constructor.
jensmaurer commentedon Jul 16, 2021
Move [stacktrace] to [diagnostics].
jensmaurer commentedon Jul 16, 2021
keep Utility types: pair, tuple, variant, optional, any, bitset under [utilities], but create a new grouping subclause called "data types".
JohelEGP commentedon Jul 16, 2021
Isn't "[charconv] Primitive numeric conversions" a good fit for Clause 26 "Numerics library"? I always searched there for it, at first.
jwakely commentedon Jul 16, 2021
Should [intseq] "Compile-time integer sequences" be a subclause of [utility] "Utility components" rather than a sibling?
jensmaurer commentedon Feb 25, 2022
Addressed with #5124