Support for reify* form #550
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
Closed
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.
Add the
reify*special form and thebasilisp.core/reifymacro for constructing reified objects.reify*allows callers to create objects of anonymous class types satisfying 0 or more Python interfaces (and Basilisp protocols when #460 merges). This was able to use most of the same code as the originaldeftype*implementation, which was convenient. It's worth noting thatreify*does not currently support classmethods (since the constructor is auto-generated and only accepts one argument -meta- anyway) or staticmethods (since the generated type is not directly exposed to users). Methods and Python properties are supported, however.Partially addresses #425