Opt-in mutable access on IndexSet, release 2.2.6 #323
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.
This adds
set::MutableValues
as an opt-in trait for accessingIndexSet
values by mutable reference, akin tomap::MutableKeys
. The implementation simply forwards to the map implementation while discarding the()
inner "value".Unlike
IndexMap
,IndexSet
doesn't have regularget_full_mut
orget_index_mut
methods, so the "2" suffix here isn't really necessary, but I thought it might be better to stay consistent withMutableKeys
on that.Closes #322