-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Various cleanups #5336
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
Merged
StephanTLavavej
merged 25 commits into
microsoft:main
from
StephanTLavavej:various-cleanups
Mar 13, 2025
Merged
Various cleanups #5336
StephanTLavavej
merged 25 commits into
microsoft:main
from
StephanTLavavej:various-cleanups
Mar 13, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Before GH 2498 on 2022-02-07, the macro was `#define _NRAND(eng, resty) (_STD generate_canonical<resty, static_cast<size_t>(-1)>(eng))` which avoided significant verbosity, but now it serves no purpose. Replaced `_NRAND\((\w+), (\w+)\)` => `_Nrand_impl<$2>($1)` because surrounding parens were never necessary.
`_Erase_tree_and_orphan_guard` calls `_Erase_tree_and_orphan`, which already uses this naming convention.
…` in `<random>`." This reverts commit 273fdca.
…issive- (strict mode) mishandles a variable template detecting static constexpr member functions".
Member
Author
|
I'm speculatively mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
davidmrdavid
approved these changes
Mar 13, 2025
Member
davidmrdavid
left a comment
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.
LGTM, just a question below.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Low-risk cleanups that I've been accumulating.
⚙️ Commits
_Is_word_tablein<regex>.P0088R3_variant_msvc.Enable=>_Enablein<variant>.if constexprforis_floating_point_vin<chrono>.if constexprforis_base_of_vinP0220R1_sample.concept available=>_HAS_CXX20in<functional>._Idl_dist_addcontrol flow in<algorithm>._NRANDmacro in<random>.#define _NRAND(eng, resty) (_STD generate_canonical<resty, static_cast<size_t>(-1)>(eng))which avoided significant verbosity, but now it serves no purpose._NRAND\((\w+), (\w+)\)=>_Nrand_impl<$2>($1)because surrounding parens were never necessary.consttounsigned int timeoutinprimitives.hpp.Change_Has_static_min_maxfromstructtoconstexpr boolin<random>./permissive-(strict mode) mishandles a variable template detectingstatic constexprmember functions", commented. (This isn't worth maintaining separate "workaround" / "no workaround" paths.)P0355R7_calendars_and_time_zones_dates.+= boolinVSO_0000000_vector_algorithms.boolis weird, so we conventionally avoid that.typenamein<format>._P_arg_type_tin<future>._mm_mfenceis SSE2; update comment after Build the x86 STL with/arch:SSE2instead of/arch:IA32#4741.inline constexprtoconstexprfor a function.while (true)=>for (;;)trueanymore, our usage remains consistent. (I don't feel super strongly about this one though.)_HAS_STD_BYTEas// TRANSITION, OS-14273702._Name.length()=>_Name.size()forstring.%[E0Q#]=>%[EOQ#]bitset.executeCommandVerboseis dead._AllocNode=>_Alnodefor consistency._Erase_tree_and_orphan_guardcalls_Erase_tree_and_orphan, which already uses this naming convention:STL/stl/inc/xtree
Lines 756 to 757 in 0d8f517