-
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 STL workarounds for VSO-1006185 #417
Conversation
...which has been fixed for 16.6p1. Fixes microsoft#416.
Blocked on release of Visual Studio 2019 16.6 Preview 1. |
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 good to me. Remember that there are workarounds in devcrt too (3 occurrences in Dev11_1140665_unique_ptr_array_conversions
); depending on when we can migrate devcrt to GitHub, you'll either need to update this PR, or add Microsoft-internal test changes.
The tests hadn't made it into the OSS repo when this PR was created.
Description
...which has been fixed for 16.6p1.
Fixes #416.
[This is a dual of internal PR MSVC-PR-222093.]
Checklist
Be sure you've read README.md and understand the scope of this repo.
If you're unsure about a box, leave it unchecked. A maintainer will help you.
_Ugly
as perhttps://eel.is/c++draft/lex.name#3.1 or there are no product code changes.
verified by an STL maintainer before automated testing is enabled on GitHub,
leave this unchecked for initial submission).
members, adding virtual functions, changing whether a type is an aggregate
or trivially copyable, etc.).
the C++ Working Draft (including any cited standards), other WG21 papers
(excluding reference implementations outside of proposed standard wording),
and LWG issues as reference material. If they were derived from a project
that's already listed in NOTICE.txt, that's fine, but please mention it.
If they were derived from any other project (including Boost and libc++,
which are not yet listed in NOTICE.txt), you must mention it here,
so we can determine whether the license is compatible and what else needs
to be done.