[Serialization] Ensure we run InheritedTypeRequest
before serializing inherited type
#78899
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.
When using
-experimental-skip-all-function-bodies
we don’t run theTypeCheckSourceFileRequest
and thus don’t go through the decl checker, which callsInheritedTypeRequest
on all inheritance clauses. This means that the inherited entries are not populated by the time we serialize the module. Trigger the computation of inherited entries by callingInheritedTypeRequest
during serialization.Unfortunately, we can’t use the type returned by
getResolvedType
for the serialization becausegetResolvedType
returns an inverted protocol type for suppressed conformances but during serialization, we want to serialize the suppressed type with aisSuppressedBit
. We thus need to callgetEntry(i).getType()
again to get the type to serialize.rdar://141440011
Thanks @hamishknight for the pointer what might be causing this issue.