Fix default witness checking [4.1] #13365
Merged
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.
Description: Fixes a type checker bug where SILGen would try to use an incomplete conformance due to a subtle phase ordering issue. Since the problem was with default witness tables and those are not used unless building a resilient module, go further and don't emit them at all unless resilience is enabled.
Scope of the issue: Reported by a user on Twitter who was hitting this with a real project.
Risk: Low, we're basically just disabling a code path for normal users.
Origination: Probably the specific crash was introduced in 4.0 when conformance access paths came along. Default witness tables have been broken in this way since first added in 3.0 or 3.1.
Tested: New test case added.
Radar: rdar://problem/35949729
Reviewed by: @jckarter