[move-only] Do not attempt to lazily deserialize the moveonly deinit table in IRGen. #66505
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 reason to avoid this is if we attempt to lazily deserialize the moveonly deinit table, we may also attempt to deserialize a deinit function. This would result in us breaking the invariant that we no longer deserialize SILFunctions once we are in LoweredSIL.
If we fail to lazily deserialize, we instead just call the deinit via the destroy value witness of the type.
This only affects builds built with asserts enabled since llvm_unreachable is compiled out when NDEBUG is set.
rdar://110496872