[Pitch] Extensible enums for non-resilient modules

[FranzBusch]

@xwu

An existing package either has to freeze all existing public enums explicitly, or break API, or not adopt the feature (or any new language mode incorporating the feature)—that is the complete set of possible options regardless of what other bells and whistles are added to roll out this feature, no? As soon as we commit to this as the plan for the language, there is no escape from making one of these choices for existing package maintainers.

Yes these are the only available choices. My disagreement was with the term "frozen in time" since packages that choose to freeze all existing public enums can still continue to evolve by adding all kinds of new APIs. They just can't change the API of the existing enums.