-
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
Remove _ITERATOR_DEBUG_ARRAY_OVERLOADS #735
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can _Array_iterator
or other machinery in <xutility>
be pushed down now?
I am unsure whether I am the best to answer that but will have a look tomorrow |
I just did a grep and it looks like that thing is only used by Thanks for your contribution! |
I moved |
This is an unrelated cleanup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great - thanks for the extensive test updates, moving the array iterators, and removing the now-unused _STL_VERIFY_ARRAY_SIZE
. You really went above and beyond!
In fact, this change was so good, I noticed that the surrounding code in the STL was bogus in comparison. Specifically, near an IDAO removal, I noticed that we were testing _HAS_IF_CONSTEXPR
within _HAS_CXX17
(which is totally unnecessary - C++17 implies if constexpr
availability). I found no other occurrences throughout the STL, so I simply pushed a commit to your PR.
Thanks so much :D |
Thanks again, @miscco! |
This fixes #660
I ran the tests that were visibly affected on my machine. That said I am curious about the tests on other architectures