Migrate ASTScope to CharSourceRanges #34207
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
|
@swift-ci Please smoke test |
|
@swift-ci Please test source compatibility |
davidungar
approved these changes
Oct 6, 2020
|
@swift-ci Please test source compatibility |
|
@swift-ci Please smoke test macOS |
slavapestov
force-pushed
the
astscope-char-source-ranges
branch
from
a3bdf0f to
e59069f
Compare
|
@swift-ci Please smoke test |
|
@swift-ci Please test source compatibility |
|
swiftlang/llvm-project#1916 |
|
@swift-ci Please test source compatibility |
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.
SourceRanges behave funny with string interpolation. A SourceRange always spans at least one token, and the end location points at the beginning of the last token that is part of the source range.
Since string literals and string interpolations are always a single token, a SourceRange that ends on a string interpolation will point at the beginning of the string interpolation. However, any source locations of expressions inside the interpolation itself now point into the middle of the string interpolation token. Eg, consider this code:
The source range of the initializer expression for
var xconsists of a single token, so it's start and end location both point at the beginning of the token"\(hello)". However, the expressionhellohas a source range consisting of the single tokenhello. Notice thathellocomes after"\(hello)" in the source file, despite being logically contained within the source range of"(hello)"`.Since ASTScope lookup relies on SourceRanges of parent nodes containing the SourceRanges of their parents, adding a child scope would sometimes have to "widen" the parent's source range. This was error-prone and complex.
Instead, we can use CharSourceRanges. Since the end location of a CharSourceRange is a byte offset of the end of the last token of the CharSourceRange, we the required invariant around nested scopes for free, without having to "widen" source ranges.
This PR adds stronger assertions for detecting children which are not contained in their parents, or overlapping sibling children.
Builds upon #34205, which fixes all the non-string-interpolation cases where source range "widening" was required.
Fixes https://bugs.swift.org/browse/SR-12997, https://bugs.swift.org/browse/SR-12999, rdar://problem/64314753, rdar://problem/64316115.