-
Notifications
You must be signed in to change notification settings - Fork 772
[sequence.reqmts] P2846 incorrectly applied for assign_range #7865
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
Comments
I believe the intent is the same. But the current wording looks a bit weird. @cor3ntin What do you think? |
The wording from https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p2846r6.pdf seems to have been incorrectly applied for |
Agreed, I don't see any mention of this in #7698 that would explain it. I think it is accidental. |
Yes, agreed, thanks! If someone sends a PR we can merge it, or I'll do it at some point. |
@jensmaurer This issue should have been fixed now. |
Fixed by 4b1283b |
In N5008 the last part of Recommended practice says "should not perform any reallocation", but the proposal said "should not perform more than a single reallocation".
Obviously, if the assigned range is larger than the current capacity, there has to be some reallocation.
The text was updated successfully, but these errors were encountered: