Fixes #2668. Reorder switch expressions to avoid flow analysis secondary issues #2693
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The fix suggested in this comment dart-lang/sdk#53392 (comment) doesn’t work. Adding
{...}
doesn’t help, but reordering does.It’s hard for me to explain why I preserved
i4
expecting no error. To me, it seems useful to have these issues somewhere in the tests. If, one day, someone fixes it (probably unintentionally), and flow analysis starts reporting an error fori4
too, then the tests will fail, and the author will know that (s)he fixed it as well.If you believe that it is not necessary, let me know, and I’ll remove it. At least there is no issue in real life. To make the code work, people have to fix all their issues, and eventually, the unreported ones become the first one and will be reported.