Frontend: Ignore lazy typechecking flags when emitting non-resilient modules #71377
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
-experimental-lazy-typecheck
and-experimental-skip-non-exportable-decls
flags are not safe to use when emitting a non-resilient module because the clients of non-resilient modules expect to have access to all the members of a type in order to e.g. compute the size the type. The-experimental-skip-non-exportable-decls
flag skips serialization of non-public members and would therefore cause mis-compilation. The-experimental-lazy-typecheck
is theoretically safe for non-resilient modules but more requestification work is needed before it can be used successfully.Resolves rdar://122272758