[4.0] IRGen: EmptyBoxType's representation cannot be nil because of a conflict with extra inhabitant assumption in indirect enums #10403
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.
Use a singleton empty heap box representation instead of nil for EmptyBoxTypes. The nil representation that we used is not compatible with assumption we make about extra inhabitant bits we make in enums.
• Explanation: Due to using an incompatible representation of empty box types and single reference enum payloads we can’t distinguish between the first empty payload case and the payload case because both map to 0.
enum Payload {
case c
}
indirect enum Test {
case a
case b(Payload)
}
Test.b(.c) // creates .a
• Scope of Issue: This has not been working since at least Xcode 8.3.f
• Risk: Low. The code path is the same for the rest of the compiler for handling reference counted payloads. This change therefore should not expose other bugs.
• Testing: Existing and added Swift CI tests