[dart-announce] Breaking change #53325: Include `on` during exhaustiveness checks

['Erik Ernst' via Dart Announcements]

Issue #53325 is a breaking change request that proposes a change to the exhaustiveness analysis performed by the analyzer (the common front end already has the desired behavior).

The change is that `on` edges from mixins to sealed types must be included for a set of types to be considered exhaustive.

Given that the common front end already reports the errors that will arise because of this change, it is likely that the change will affect a very small amount of code, if any at all.

Nevertheless, please comment on the issue in case you expect this change to cause significant breakage in your Dart code.

  best regards,

--

Erik Ernst  -  Google Danmark ApS

Skt Petri Passage 5, 2 sal, 1165 København K, Denmark

CVR no. 28866984

--
For more ways to connect visit https://dart.dev/community