Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restructure [utilities] #3388

Closed
jensmaurer opened this issue Nov 8, 2019 · 6 comments
Closed

Restructure [utilities] #3388

jensmaurer opened this issue Nov 8, 2019 · 6 comments

Comments

@jensmaurer
Copy link
Member

jensmaurer commented Nov 8, 2019

Ideas from Belfast editorial session:

  • Utility types: pair, tuple, variant, optional, any, bitset
  • Memory management: memory, smart Pointers, memory resource, scoped_allocator-adaptor,
  • Compile-time programming: type_traits, ratio
@jensmaurer
Copy link
Member Author

Move [format] to [strings], since it's essentially a fancy string constructor.

@jensmaurer
Copy link
Member Author

Move [stacktrace] to [diagnostics].

@jensmaurer
Copy link
Member Author

keep Utility types: pair, tuple, variant, optional, any, bitset under [utilities], but create a new grouping subclause called "data types".

@JohelEGP
Copy link
Contributor

Isn't "[charconv] Primitive numeric conversions" a good fit for Clause 26 "Numerics library"? I always searched there for it, at first.

@jwakely
Copy link
Member

jwakely commented Jul 16, 2021

Should [intseq] "Compile-time integer sequences" be a subclause of [utility] "Utility components" rather than a sibling?

@jensmaurer
Copy link
Member Author

Addressed with #5124

C++23 clause renumbering automation moved this from Open to Done Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants