Break cyclic dependency due to implicit initialization of optional properties #63431
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
…lues The fundamental problem here is that we don't know a priori whether an accessor macro will convert a stored property into a computed one. That can only be determined after macro expansion, which depends on having a determined type for the property. Implicit initialization of optional-typed values (e.g., "var birthDate: Date?") adds the initializer when there is storage, triggering the cycle. Introduce a very narrow fix that assumes that properties that have an accessor macro on them do not have storage. We probably want to enforce this, so that the "does this variable have storage?" query can be made cheaper.
DougGregor
requested review from
hborla,
slavapestov and
xedin
as code owners
Member
Author
|
@swift-ci please smoke test and merge |
Member
Author
|
@swift-ci please smoke test Linux |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The fundamental problem here is that we don't know a priori whether an accessor macro will convert a stored property into a computed one. That can only be determined after macro expansion, which depends on having a determined type for the property.
Implicit initialization of optional-typed values (e.g., "var birthDate: Date?") adds the initializer when there is storage, triggering the cycle. Introduce a very narrow fix that assumes that properties that have an accessor macro on them do not have storage. We probably want to enforce this, so that the "does this variable have storage?" query can be made cheaper.