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

LWG-2261 Are containers required to use their 'pointer' type internally? #72

Open
StephanTLavavej opened this issue Sep 6, 2019 · 2 comments
Labels
LWG Library Working Group issue vNext Breaks binary compatibility

Comments

@StephanTLavavej
Copy link
Member

StephanTLavavej commented Sep 6, 2019

LWG-2261 Are containers required to use their 'pointer' type internally?

vNext note: Resolving this issue will require breaking binary compatibility. We won't be able to accept pull requests for this issue until the vNext branch is available. See #169 for more information.

@StephanTLavavej StephanTLavavej added LWG Library Working Group issue vNext Breaks binary compatibility labels Sep 6, 2019
@BillyONeal
Copy link
Member

Note that we actually comply with this now in _IDL0 mode.

@StephanTLavavej StephanTLavavej changed the title LWG 2261 Are containers required to use their 'pointer' type internally? LWG-2261 Are containers required to use their 'pointer' type internally? Oct 23, 2019
@cbezault cbezault modified the milestone: Conformance May 7, 2020
@frederick-vs-ja
Copy link
Contributor

frederick-vs-ja commented Feb 22, 2024

Per WG21-P0773R0, it seems that only deque needs to be fixed (modulo _Iterator_base12).

Edit: vector<bool>'s iterators may also need to be fixed.

const _Vbase* _Myptr = nullptr;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LWG Library Working Group issue vNext Breaks binary compatibility
Projects
Status: Blocked
Development

No branches or pull requests

4 participants