-
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
Relocate endian to <bit> #305
Relocate endian to <bit> #305
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.
This change looks good. You should know that you're racing @barcharcraz to add <bit>
; the loser will have to resolve the merge conflicts. ;)
EDIT: The CI failure is about line endings in <bit>
: you have LF endings, and we require CRLF.
Co-Authored-By: Casey Carter <cartec69@gmail.com>
Co-Authored-By: Stephan T. Lavavej <stl@nuwen.net>
my PR is up at #310 The race is on ;D |
I am porting this to our Microsoft-internal MSVC repo and running tests; when that's successful, I'll merge your PR here, and we'll rebase Charlie's PR accordingly. |
Merged for VS 2019 16.5 Preview 2. Thanks again, and congratulations on implementing your first C++20 feature here! |
Description
Resolves #61
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.