Reorganize libc++ skips#3464
Conversation
CaseyCarter
commented
Feb 13, 2023
- All "libc++ doesn't implement (some proposal or LWG issue)" comments should be in the "ISSUES REPORTED/KNOWN UPSTREAM" section: libc++ knows what work WG21 has approved as well as we do.
- Strike noise word "yet" from all comments (e.g., "not yet implemented", "not yet analyzed")
- order "MISSING STL FEATURES" by proposal number
* All "libc++ doesn't implement (some proposal or LWG issue)" comments should be in the "ISSUES REPORTED/KNOWN UPSTREAM" section: libc++ knows what work WG21 has approved as well as we do. * Strike noise word "yet" from all comments (e.g., "not yet implemented", "not yet analyzed") * order "MISSING STL FEATURES" by proposal number
|
Verified no divergence between the files. I couldn't resist resetting testing when I saw a pre-existing typo 😸 I will note that I can't think of a more conflict-prone time to perform such a cleanup than right after a batch of C++23 features and LWG issues appeared, but it's not actually that annoying to resolve such conflicts. 😹 |
LMK if you do think of a more conflict-prone time so I can close this and resubmit. |
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
|
I've pushed a merge with |
|
Thanks for the cleanup! 🧹 ✨ 🪄 |