Fetcher api for multiple mutable value access.
#47
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
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.
This is intended as an initial discussion PR and not a completed/documented feature. While the feature will work as submitted. I believe more discussion is required, and an obvious clean up would be due.
I am often burdened by the lack of aliasing hints for the rust compiler and end up wanting multiple mutable access to data that should be completely safe. Since there is no way to tell a method what it aliases, it is automatically assumed that it aliases over the entire struct that it is attached to.
Because of the above, it is impossible to get multiple mutable values out of a map. This PR is an attempt to create a discussion around a potential solution to that problem.
Please let me know what you think.