You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See #33 (comment) / #34. This was discussed but left out to match the very similar TextEncoder.prototype.encodeInto, which doesn't have such a parameter.
Well, set is directly attached to Uint8Array where TextEncoder.encodeInto is not. So I don't thing we should compare or align both . Moreover the necessity to perform a trick on TextEncoder.encodeInto feels... wrong.
Writing data at specific a position is a common practice with encoders/decoders, and I think we should keep simplicity and efficiency when possible.
For the record, I’m sympathetic to this intuition. There’s no world where working around this limitation with a subarray allocation would be faster than passing an offset. I like having the option.
Hi,
I'm playing with this new api, and I thing it could be great to have an
offset
argument on thesetFromBase64/Hex
methods:Issue: on mdn
In my opinion, this feels sub-optimal.
Proposal:
We could mimic the .set method.
What do you think ?
The text was updated successfully, but these errors were encountered: