-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Eliminate Observable circular reference errors via lazier TypeRefinementContext building #67642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
DougGregor
merged 7 commits into
swiftlang:main
from
DougGregor:lazy-type-refinement-context
Aug 3, 2023
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b5d3e0b
[Type refinement context] Don't query property wrappers just for rang…
DougGregor 3079f3d
[Type refinement context] Lazily expand TRCs for pattern bindings
DougGregor 50ca096
Make `VarDecl::isLayoutExposedToClients` check property wrappers more…
DougGregor 0d779df
[Type refinement context] Avoid creating implicit contexts with bad r…
DougGregor c098175
Add test case involving circular references with `@Observable`
DougGregor 7f031df
Drop unnecessary "parent context" state from TypeRefinementContextBui…
DougGregor 37959de
Establish type refinement contexts for pattern binding decls directly
DougGregor File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2079,19 +2079,23 @@ bool VarDecl::isLayoutExposedToClients() const { | |
if (!parent) return false; | ||
if (isStatic()) return false; | ||
|
||
if (!hasStorage() && | ||
!getAttrs().hasAttribute<LazyAttr>() && | ||
!hasAttachedPropertyWrapper()) { | ||
return false; | ||
} | ||
|
||
auto nominalAccess = | ||
parent->getFormalAccessScope(/*useDC=*/nullptr, | ||
/*treatUsableFromInlineAsPublic=*/true); | ||
if (!nominalAccess.isPublic()) return false; | ||
|
||
return (parent->getAttrs().hasAttribute<FrozenAttr>() || | ||
parent->getAttrs().hasAttribute<FixedLayoutAttr>()); | ||
if (!parent->getAttrs().hasAttribute<FrozenAttr>() && | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is it worth adding a comment here pointing out that we want to check the "easy" conditions before possibly evaluating requests? |
||
!parent->getAttrs().hasAttribute<FixedLayoutAttr>()) | ||
return false; | ||
|
||
if (!hasStorage() && | ||
!getAttrs().hasAttribute<LazyAttr>() && | ||
!hasAttachedPropertyWrapper()) { | ||
return false; | ||
} | ||
|
||
return true; | ||
} | ||
|
||
/// Check whether the given type representation will be | ||
|
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, it feels like there's some overlap here with the
parentDeclForInferredAvailability
function that I introduced. I don't know that the two can merge, but maybeparentDeclForInferredAvailability
should call this?