Re: [whatwg/encoding] Define encodeInto() API (#166)

I think this is implied by your last comment, but just to confirm: as written, _destination_'s view bounds (offset, length) onto its ArrayBuffer is seemingly ignored by the current algorithm. i.e. in this case:
```js
const ab = new ArrayBuffer(5);
const ua = new Uint8Array(ab, 1, 2);
new TextEncoder().encodeInto("ABCDE", ua);
```
... I would expect `ab` to end up as [0, 0x65, 0x66, 0, 0]. 

(I don't see test cases for this either)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/pull/166#issuecomment-447077999