Generalize vectorized bitset::to_string implementation#5013
Merged
StephanTLavavej merged 6 commits intomicrosoft:mainfrom Oct 21, 2024
Merged
Generalize vectorized bitset::to_string implementation#5013StephanTLavavej merged 6 commits intomicrosoft:mainfrom
bitset::to_string implementation#5013StephanTLavavej merged 6 commits intomicrosoft:mainfrom
Conversation
bitset::to_string implementation
StephanTLavavej
approved these changes
Oct 17, 2024
Member
|
Thanks, I like this approach! 😻 I pushed a conflict-free merge with |
Member
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Member
|
Thanks for refactoring this code! 🖥️ ⚙️ 🪄 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Not an optimization, rather maintenance change.
Experience with bitset from string and others has shown that while traits-based approach is a bit harder to read, it is less error prone.
The benchmark results are within the same.
The only semantic change is that now
memcpyis always used for tail, instead of just one specific case where tail can be long.