AST: attempt to rewrite the expression to be more legible #26132
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
This restores the original spelling of the restriction. This is more legible and may be something which VS2017 will handle properly. Thanks to @drodriguez for suggesting this!
|
@swift-ci please test Windows platform |
|
The error seems not related. I’m on mobile, but it seems to me that the CHECK line should match the one that is printed. Sent with GitHawk |
|
@swift-ci please test |
|
@swift-ci please test Windows platform |
1 similar comment
|
@swift-ci please test Windows platform |
broadwaylamb
pushed a commit
to broadwaylamb/swift
that referenced
this pull request
Jul 15, 2019
AST: attempt to rewrite the expression to be more legible
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.
This restores the original spelling of the restriction. This is more
legible and may be something which VS2017 will handle properly.
Thanks to @drodriguez for suggesting this!
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves SR-NNNN.