[WIP] Improve and complete Mirror API #105
Open
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
smarr
added
bug
smarr
changed the title
Signed-off-by: Stefan Marr <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
[This is a work-in-progress PR, mostly to have an issue to work on, and to keep notes on some existing patches.]
The Mirror API needs to be made complete and consistent.
Currently it is not even possible to navigate the basic relations in object model, for instance superclass relationships as well as class/metaclass relations.
The attached patch and example program shows how it could be used. But, the current mirror design is not yet good. Method names are ambiguous, sometimes it is unclear on what a mirror works, and generally how they are used to travers an object model.