<xmemory>: Tolerate bogus const-overloading in iterators passed to uninitialized_meow()#5170
Merged
StephanTLavavej merged 2 commits intomicrosoft:mainfrom Dec 13, 2024
Conversation
CaseyCarter
approved these changes
Dec 7, 2024
Member
Author
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
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
2 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.
std::uninitialized_move/_nand guaranteed copy elision #5135.operator*with varying return types llvm/llvm-project#119084.'const llvm::Value *'to'_Ty'".In an ideal world with infinite capacity, we would push through RWC fixes as we did with #5105. However:
#include <chrono>.uninitialized_meow()is relatively obscure.