Do not require mut on ParsedPath::element_mut #8891
Merged
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.
Objective
ParsedPath
does not need to be mut to access a field of aReflect
. Be that access mutable or not. Yetelement_mut
requires a mutable borrow onself
.Solution
element_mut
take a&self
over a&mut self
.#8887 fixes this, but this is a major limitation in the API and I'd rather see it merged before 0.11.
Changelog
ParsedPath::element_mut
andParsedPath::reflect_element_mut
now accept a non-mutableParsedPath
(only the accessedReflect
needs to be mutable)