> On Oct 12, 2017, at 3:52 AM, Geordie Jay via swift-users > <swift-users@swift.org> wrote: > > > Guillaume Lessard via swift-users <swift-users@swift.org > <mailto:swift-users@swift.org>> schrieb am Mi. 11. Okt. 2017 um 23:49: > A lot of the MutableCollection implementation is in protocol extensions > (swapAt, for example.) > > Should an additional version be written just for the Unsafe*BufferPointer > types? > > Makes sense to me, given the examples above. It doesn’t seem to be a high > priority task though, and one one suited to a contributor pull request rather > than taking resources away from the core team. > > Would this kind of change need to go through swift evolution or is it a “no > brainer”? > > Geordie
I’ll just point out that it’s already the case that methods defined in Unsafe*BufferPointer that write to memory are “nonmutating”. So I think it’s both a “no brainer” and needs to go through evolution. -Andy
_______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
