Skip to content

[Sealed class] Implement feature in the CFE #51280

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
Tracked by #51278
itsjustkevin opened this issue Feb 6, 2023 · 4 comments
Closed
Tracked by #51278

[Sealed class] Implement feature in the CFE #51280

itsjustkevin opened this issue Feb 6, 2023 · 4 comments
Labels
legacy-area-front-end Legacy: Use area-dart-model instead.
Milestone

Comments

@itsjustkevin
Copy link
Contributor

No description provided.

@srawlins
Copy link
Member

srawlins commented Feb 6, 2023

CC @kallentu

@devoncarew devoncarew added the legacy-area-front-end Legacy: Use area-dart-model instead. label Feb 7, 2023
@johnniwinther
Copy link
Member

@kallentu Is there anymore work needed for the CFE?

@kallentu
Copy link
Member

kallentu commented Feb 7, 2023

@kallentu Is there anymore work needed for the CFE?

The only thing I have left to do for sealed for the CFE is some changed behaviour with its interaction with base and final. I guess for the sealed feature on its own, everything is done.
Closing.

@kallentu kallentu closed this as completed Feb 7, 2023
@srawlins
Copy link
Member

srawlins commented Feb 7, 2023

Yeah definitely a downside of having separate language features. But it's all just tracking info, 🤷 . Thanks!

@johnniwinther johnniwinther removed the Epic label May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-front-end Legacy: Use area-dart-model instead.
Projects
None yet
Development

No branches or pull requests

5 participants