[Sema] Fix #84644: Implicit initializers now inherit default actor isolation. #84815
+13 −1
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.
Resolves #84644
Problem:
When a class and its subclass have no explicit initializers, the compiler would emit:
This occurs under Swift 6.2 with default
@MainActor
isolation enabled. The synthesized default initializer for the superclass was not inheriting the class’s default actor isolation, causing a mismatch when a subclass implicitly overrides it.Solution:
Ensure that synthesized default initializers inherit the class’s default actor isolation:
This guarantees compatibility between synthesized initializer of superclass and any of its subclass, even if neither declares an explicit init().
Regression Test:
Added test/concurrency/default_actor_isolation_initializer.swift:
The test confirms that classes without explicit initializers now compile correctly when default actor isolation is applied.
Impact:
@MainActor
classes with implicit initializers.