Skip to content
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

Support 2.0 in the analyzer independent of the new front end #31640

Closed
8 of 14 tasks
bwilkerson opened this issue Dec 13, 2017 · 6 comments
Closed
8 of 14 tasks

Support 2.0 in the analyzer independent of the new front end #31640

bwilkerson opened this issue Dec 13, 2017 · 6 comments
Labels
area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). P1 A high priority bug; for example, a single project is unusable or has many test failures

Comments

@bwilkerson
Copy link
Member

bwilkerson commented Dec 13, 2017 •
edited
Loading

This is a tracking issue for supporting the Dart 2.0 semantics in analyzer without using the new front end.

Moved to post alpha2:
@bwilkerson bwilkerson added area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. P1 A high priority bug; for example, a single project is unusable or has many test failures area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). labels Dec 13, 2017
@devoncarew devoncarew mentioned this issue Dec 13, 2017
Closed
37 tasks
@devoncarew
Copy link
Member

@MichaelRFairhurst, I added a line above for re-evaluate deferred work for supporting generic function type syntax (discussed in person).

@devoncarew
Copy link
Member

Updated the first line item with a resolution re: using flags to enable these features.

@stereotype441 stereotype441 mentioned this issue Jan 5, 2018
Closed
whesse pushed a commit that referenced this issue Jan 8, 2018
@jwren
Create the new flag --use-cfe in the analyzer, analysis server and an…
cd878bc 
…alyzer_cli and migrate the old behavior of --preview-dart-2 to --use-cfe. The --preview-dart-2 flag is now a no-op, with functionality coming soon.

See #31640

Change-Id: I2db2e7ef6a324cbd5d369b807e331495fed167df
Reviewed-on: https://dart-review.googlesource.com/33121
Reviewed-by: Konstantin Shcheglov <[email protected]>
Commit-Queue: Jaime Wren <[email protected]>
@devoncarew devoncarew added this to the 2.0-alpha2 milestone Jan 26, 2018
@MichaelRFairhurst
Copy link
Contributor

Updated to show that #30177 is closed

@bwilkerson
Copy link
Member Author

I believe that this issue is now obsolete. Please re-open if that's not true.

@stereotype441
Copy link
Member

The checkbox for #31638 is not yet checked. That bug is incomplete because its checkbox for #32156 is not yet checked. #32156 is still being worked on by @jmesserly - see https://dart-review.googlesource.com/c/sdk/+/45141. I'm going to ping that CL in the hopes that it can be landed soon, and I'll adjust #32156's priority to P1 to match this bug.

@stereotype441 stereotype441 reopened this Mar 22, 2018
@stereotype441 stereotype441 mentioned this issue Mar 22, 2018
Closed
@stereotype441
Copy link
Member

All remaining unfinished subtasks are now being tracked in #32395.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@stereotype441 @devoncarew @MichaelRFairhurst @bwilkerson