UnicodeScalarView conform to
RangeReplaceableCollection, so is there a reason why their associated
UTF16Views don't as well? Couldn't it be helpful for working with a string's underlying representation in a performant way? Or is there a "better" way to modify a string's bytes?
If this conformance does seems like a good addition, what is the path forward? Swift Evolution pitch?