-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
P0843R14 <inplace_vector>
#4766
Comments
I have implemented this here: https://github.com/vasama/MSSTL/tree/feature/inplace_vector When you start accepting C++26 features, I will be happy to reopen and update my PR. |
A proxy object for container/iterator debugging will make the container totally non-trivial, which is fine for all containers but Do we want to add a proxy object (but shouldn't be dynamically allocated if added) for debugging when it's allowed to do so? |
Dynamically allocated proxy objects are a bane, and we should avoid adding any more. There's no point in container-internal proxy objects - their whole purpose is to allow iterators to find their parents after swapping/moving. (Note the distinction between them and sentinel nodes. Container-internal sentinel nodes work because they don't remain valid after swapping/moving.) |
In my implementation the debug iterator currently contains a pointer directly to the size member of the |
WG21-P0843R14
<inplace_vector>
Feature-test macro:
Note: We're focused on implementing the remaining library-only features in C++23. Until that's done, we will NOT be accepting PRs for C++26 features.
The text was updated successfully, but these errors were encountered: