Re: [swift-evolution] Questions about non-exhaustive enums

Good questions. The answer at a high level is "you break binary and source compatibility", and if you care about binary compatibility everything will fall to pieces (read: crashes, possibly undefined behavior). So our only goal on the binary compatibility is to make the "falling to pieces" as de

Re: [swift-evolution] Questions about non-exhaustive enums

This is the same issue as when a library maintainer changes a class from open to closed. > On Jan 5, 2018, at 10:54 AM, Ignacio Soto via swift-evolution > wrote: > > I love the revision to the proposal > , but I have a couple of > remaining

[swift-evolution] Questions about non-exhaustive enums

I love the revision to the proposal , but I have a couple of remaining questions that don't seem to be addressed in the doc and I'm curious about: - What happens if a library maintainer adds a new case to a *@frozen* enum? - What happens