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

core library updates for super-initializer parameters #48066

Closed
Tracked by #48055
devoncarew opened this issue Jan 4, 2022 · 2 comments
Closed
Tracked by #48055

core library updates for super-initializer parameters #48066

devoncarew opened this issue Jan 4, 2022 · 2 comments
Assignees
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.

Comments

@devoncarew
Copy link
Member

devoncarew commented Jan 4, 2022

See #48055 for the main tracking issue.

@devoncarew devoncarew changed the title core library updates for super-initializer parameters (todo:) core library updates for super-initializer parameters Jan 4, 2022
@devoncarew devoncarew added the area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. label Jan 4, 2022
@devoncarew
Copy link
Member Author

cc @lrhn

@lrhn
Copy link
Member

lrhn commented Apr 3, 2022

There are no necessary changes to the platform libraries for super-initializer parameters.

We can consider whether we want to showcase the feature in some cases where it applies. I don't expect that to be many cases in public classes, since we often have a public interface/private implementation separation, where users won't see the actual generative constructors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.
Projects
None yet
Development

No branches or pull requests

3 participants