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.

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

Meta-issue for "why not promoted" functionality #44897

Open
7 of 15 tasks
stereotype441 opened this issue Feb 9, 2021 · 0 comments
Open
7 of 15 tasks

Meta-issue for "why not promoted" functionality #44897

stereotype441 opened this issue Feb 9, 2021 · 0 comments
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). 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 Feb 9, 2021

This is a meta-issue for tracking progress towards "why not promoted" functionality for the Dart toolchain. It comprises the following arcs of work:

@stereotype441 stereotype441 added area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). type-enhancement A request for a change that isn't a bug P2 A bug or feature request we're likely to work on labels Feb 9, 2021
@stereotype441 stereotype441 added this to the Future milestone Feb 9, 2021
dart-bot pushed a commit that referenced this issue Apr 1, 2021
These tests just cover the CFE functionality.  Once
#44905 is addressed, I'll add
test expectations for the analyzer.

Note: these tests uncovered two unreelated bugs: #45551 and #45552.

Bug: #44897
Change-Id: I465b157afc2cc15bcc5ce083aaa74614313a38a6
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/193581
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Leaf Petersen <leafp@google.com>
Reviewed-by: Bob Nystrom <rnystrom@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). 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

1 participant