Re: [whatwg/encoding] Make decode() and encodeInto() accept SharedArrayBuffer-backed views (#172)

I think from a specification-perspective the only thing that's needed here is adding `[AllowShared]`, right? (I.e., IDL does not allow directly passing a `SharedArrayBuffer` (without a view) and that's okay.) Copying input for `decode()` and writing output in a single go for `encodeInto()` is both high-level and vague enough to allow the various races that might occur.

I suspect we might want to add a note for those races and I'd appreciate help drafting that.

(And we'll need tests.)

@juj if null-terminated strings continue to be a compelling enough problem to address with builtin functionality, could you please file a separate issue on that? I think it's largely separable from shared memory use cases and I'd like not to do too much in one place.

-- 
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/issues/172#issuecomment-505015370