the index_mut implementation should also support index types other than usize to support batch editing operations ("copy N bytes into these N bytes of the source")
the existing implementation restricted the index type to just usize so that this information could be used to inform caching strategies
this PR relaxes the constraint for now, with the caveat that we will likely need to constrain the implementation a bit so we can actually get the indexing data during a call to index_mut (e.g. only allow index_mut for usize and the Range family of index types) so we can concretely get the actual indexes mutated
the
index_mutimplementation should also support index types other thanusizeto support batch editing operations ("copy N bytes into these N bytes of the source")the existing implementation restricted the index type to just
usizeso that this information could be used to inform caching strategiesthis PR relaxes the constraint for now, with the caveat that we will likely need to constrain the implementation a bit so we can actually get the indexing data during a call to
index_mut(e.g. only allowindex_mutforusizeand theRangefamily of index types) so we can concretely get the actual indexes mutated