[5.9][TypeChecker/DI] InitAccessors: Treat properties without "initializes" as stored fix default initialization handling #68051
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.
Cherry-pick of #67763, #67769
A couple of improvements to init accessors feature to align implementation with the proposal.
If an init accessor property doesn't initialize any stored properties it has to be initialized explicitly unless it has initializer expression;
Init accessor properties without initializer expressions suppress default initializers;
Scope: Init accessors that do not initialize stored properties.
Main Branch PRs: [DI] Properties with init accessors without "initializes" act as stored #67763, [TypeChecker] InitAccessors: Fix default initialization of init accessor properties #67769
Resolves: rdar://113401979, rdar://113421273
Risk: Low
Reviewed By: @hborla
Testing: Added test-cases to the suite.
Resolves: rdar://113401979
Resolves: rdar://113421273