Skip to content

Change core libraries as needed in order to use or work well with constructor tearoffs #46245

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
Closed
eernstg opened this issue Jun 3, 2021 · 1 comment
Closed

Change core libraries as needed in order to use or work well with constructor tearoffs #46245

eernstg opened this issue Jun 3, 2021 · 1 comment
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.

Comments

@eernstg
Copy link
Member

eernstg commented Jun 3, 2021 •
edited
Loading

This issue tracks support of the constructor tearoffs feature. See the enclosing meta-issue for details.
@eernstg eernstg added the area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. label Jun 3, 2021
@eernstg eernstg mentioned this issue Jun 3, 2021
Closed
20 tasks
@lrhn
Copy link
Member

lrhn commented Jun 25, 2021

There are no planned changes to the platform libraries.
We may want to use the feature, in cases where we currently eta-expand a constructor instead of tearing it off, but that's neither urgent nor important and can be fixed at any later time. It should not block release of the feature.

@lrhn lrhn closed this as completed Jun 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lrhn @eernstg