Make dyn Node more usable.
#83
Merged
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
|
@IvanUkhov what do you think about this PR? |
flosse
reviewed
Sep 16, 2024
flosse
reviewed
Sep 16, 2024
Co-authored-by: Markus Kohlhase <mail@markus-kohlhase.de>
Co-authored-by: Markus Kohlhase <mail@markus-kohlhase.de>
|
Thank you! |
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.
The
Nodetrait currently is the only way to interact with any element in the tree in a type-safe manner viaBox<dyn Node>. This PR adds new behaviors to theNodetrait and its implementation generators that allow it to:dyn Nodeis, though not via the Rust type system.dyn Nodeimmutably or mutably.While it would be possible to do this cleanly, I suspect it'd be difficult to do without breaking things.