Extract Payload for enum cases having associated value

[GLanza (Giuseppe Lanza)]

The last 2 answers from @Tino synthesize why we shouldn't have synthesized properties:

Automatically derive properties for enum cases

So it's better to have a sea of properties that are created no matter wether you need them or not? Which would interfere with properties that developers created because they are actually required for their code? Which need rules for all kinds of edge cases right in the compiler? Don't understand me wrong, I already wrote that it's fine for me if people use the the techniques outlined in this thread - I just don't think it's good to put all of this into the compiler. Taking you example of FSM:…

I'll add:

• to avoid overloading issues naming should be really weird and verbose. notRequestedWithShouldRequest
• extensions of Collection, AnyPublisher, Observable, Signal would be impossible

extension Collection where Element: ???? { }

If you believe that having properties will cover more use cases, then we can agree to disagree. Generic function with protocol (similarly to the existent CaseIterable) is in my opinion the way to go, and it is what I'm pitching now. To propose something completely different is acceptable, but I believe it deserve another topic.