[Windows]: explicitly set closure captures #60647
Merged
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
MSVC isn't seeing that `CheckDefaultInitializer` is declared and being implicitly captured by reference by the closure going into the `forEachVariable`. Capturing `HasStorage` and `CheckDefaultInitializer` explicitly.
|
@swift-ci please test |
compnerd
approved these changes
Aug 19, 2022
|
It's most definitely horrible. MSVC should be able to see that those variables are declared right there. If you know of another way to communicate that, I'm all ears. |
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.
MSVC isn't seeing that
CheckDefaultInitializeris declared and beingimplicitly captured by reference by the closure going into the
forEachVariable.Capturing
HasStorageandCheckDefaultInitializerexplicitly.