Skip to content

Analyzer: control flow collections phase 2 #35567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task done
stereotype441 opened this issue Jan 4, 2019 · 2 comments
Closed
1 task done

Analyzer: control flow collections phase 2 #35567

stereotype441 opened this issue Jan 4, 2019 · 2 comments
Labels
implementation Track the implementation of a specific feature (use on area-meta issue, not issues for each tool) legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on type-enhancement A request for a change that isn't a bug

Comments

@stereotype441
Copy link
Member

stereotype441 commented Jan 4, 2019 •
edited by bwilkerson
Loading

Phase 2 covers tool support. For the analyzer this means high quality error messages, parser recovery, and quick fixes.

Note that this should be behind an experimental flag.

See the language tracking issue: dart-lang/language#165
And the feature specification: https://github.com/dart-lang/language/blob/master/accepted/future-releases/control-flow-collections/feature-specification.md
And the implementation plan: https://github.com/dart-lang/language/blob/master/accepted/future-releases/control-flow-collections/implementation-plan.md

Subtasks include:
@stereotype441 stereotype441 added legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on type-enhancement A request for a change that isn't a bug labels Jan 4, 2019
@munificent munificent mentioned this issue Jan 4, 2019
Closed
18 tasks
@bwilkerson
Copy link
Member

I don't know whether there is more work here that we wanted to get done or whether we should close this.

@stereotype441
Copy link
Member Author

I'm happy to consider it done at this point.

@eernstg eernstg added the implementation Track the implementation of a specific feature (use on area-meta issue, not issues for each tool) label Jul 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
implementation Track the implementation of a specific feature (use on area-meta issue, not issues for each tool) legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on type-enhancement A request for a change that isn't a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stereotype441 @bwilkerson @eernstg