Skip to content

Analyzer: spread collections phase 1 #35569

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.

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

Closed
7 tasks done
stereotype441 opened this issue Jan 4, 2019 · 3 comments
Closed
7 tasks done

Analyzer: spread collections phase 1 #35569

stereotype441 opened this issue Jan 4, 2019 · 3 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
Milestone

Comments

@stereotype441
Copy link
Member

stereotype441 commented Jan 4, 2019

Phase 1 covers foundational support, i.e. parsing the new syntax, type checking it, and evaluating ... in constant collections.

Note that this should be behind an experimental flag.

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

Remaining tasks 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
@stereotype441
Copy link
Member Author

Note that the language team is currently writing tests for this feature: https://dart-review.googlesource.com/c/sdk/+/89085

@bwilkerson
Copy link
Member

I have checked off the classes for which the necessary changes have already been committed. I have pending changes for several of the remaining classes, but didn't want to mark them as complete before they're committed.

Is SourceVisitor the class by that name in dart_style, or the class named _SourceVisitor in analyzer? If it's the former, then it probably shouldn't be on this list. If it's the latter then we should rename it and mark it complete (because it doesn't require any changes).

@stereotype441
Copy link
Member Author

Is SourceVisitor the class by that name in dart_style, or the class named _SourceVisitor in analyzer? If it's the former, then it probably shouldn't be on this list. If it's the latter then we should rename it and mark it complete (because it doesn't require any changes).

It was the one in dart_style. I've removed it from the list.

@stereotype441 stereotype441 added this to the Dart2.3 milestone Mar 19, 2019
@stereotype441 stereotype441 modified the milestones: Dart 2.3, Dart 2.4 Apr 4, 2019
@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
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
Development

No branches or pull requests

3 participants