Skip to content

Implement external and abstract variables #42560

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
5 of 6 tasks
eernstg opened this issue Jul 2, 2020 · 8 comments
Closed
5 of 6 tasks

Implement external and abstract variables #42560

eernstg opened this issue Jul 2, 2020 · 8 comments
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). Epic implementation Track the implementation of a specific feature (use on area-meta issue, not issues for each tool) type-enhancement A request for a change that isn't a bug

Comments

@eernstg
Copy link
Member

eernstg commented Jul 2, 2020

This is the tracking issue for implementing external variables and abstract instance variables, as specified here. The implementation plan is here.

Subtasks (with check boxes for the ones that aren't issues in this epic):

@eernstg eernstg added the Epic label Jul 2, 2020
@vsmenon vsmenon added the area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). label Jul 22, 2020
@vsmenon
Copy link
Member

vsmenon commented Jul 22, 2020

@leafpetersen @franklinyow - do we have a particular release we're aiming for yet?

@eernstg
Copy link
Member Author

eernstg commented Jul 22, 2020

The feature is controlled by the non-nullable experiment flag, so presumably it's synchronized with null safety.

@leafpetersen
Copy link
Member

Yes, this feature is intended to ship with the null safety release, and both the analyzer and the CFE are on board with that timing (@stereotype441 will contribute substantially to the analyzer implementation, which I believe is already in progress).

@vsmenon
Copy link
Member

vsmenon commented Jul 23, 2020

Thanks.

@franklinyow - are we tracking this for null safety beta work?

@franklinyow
Copy link
Contributor

Added this under Beta Epic

@leafpetersen
Copy link
Member

Looks like this is close to done. Other than dartpad, any other work we're tracking?

@eernstg
Copy link
Member Author

eernstg commented Sep 4, 2020

The language specification work will be done after the stable 2.8 spec is out, and we don't otherwise consider that step to be blocking.

@leafpetersen
Copy link
Member

I think this is done.

@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
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). Epic implementation Track the implementation of a specific feature (use on area-meta issue, not issues for each tool) type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

4 participants