Use PyType instances instead of raw pointers #1431
Merged
Conversation
This file contains hidden or 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
7ea7773 to
9e0b6d8
Compare
199f493 to
93a1313
Compare
93a1313 to
9582366
Compare
…e and ConstructorBinding instances
9582366 to
47107d1
Compare
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.
Use
PyTypeinstances instead of raw pointers inTypeManagertype cache andConstructorBindinginstancesWhat does this implement/fix? Explain your changes.
This is part of an effort to clear up reference ownership story for various implementations of CLR metaclass.
Does this close any currently open issues?
No