[Backport 2.16] CoreObject native class compatibility #16806
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Backports the recent changes to CoreObject, along with changes to init order proposed in RFC 337.
pzuraq
force-pushed
the
backport-core-object-init-2-16
branch
from
12c55e2
to
28dce93
Compare
|
@rwjblue @kategengler 2.16 is no longer supported, right? so I'm assuming this can be closed? |
|
I'd say this is still a stretch goal for the polyfill, but we probably won't have time in the near future, and this branch would definitely have to be worked on a fair amount. We can close for now and I can reopen when it's ready. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backports the recent changes to CoreObject, along with changes to init
order proposed in RFC 337.