Issue Description:

I have run into an issue where the compiler is emitting the wrong value for an enum case at a call-site which in turn causes unexpected behaviour downstream when the value is pattern matched.

I have been able to reproduce with this trivial example:

import SwiftUI

enum Foo {
    case one
    case two(ScenePhase)
    case three
    case four(Bool)
    case five
    case six
    case seven
}

print(Foo.seven)     // prints "one"

I have also observed that the issue goes away when:

• there are six cases only and not seven

• the ScenePhase payload is replaced with a different type such as String

• the Bool payload is removed so there is only a single associated type of ScenePhase

Others have observed this may be happening when using associated values that are non-frozen resilient enum types, see discussion here.