Mark S. Miller
Mark S. Miller
I do agree. Please reraise this specific issue. On Thu, Jul 28, 2016 at 5:32 PM, Jordan Harband [email protected] wrote: > Unfortunately I missed the rationale for that, but it...
See also - https://github.com/endojs/endo/pull/701
Just noting that #2109 is related, but would not close this bug.
Attn @phoddie
To shim making an ArrayBuffer itself read-only, we'd need a way to actually make an ArrayBuffer read-only in place. The only thing we know how to shim would be something...
> replace the TypedArray and ArrayBuffer constructors Doh! I'm embarrassed that I didn't think of this. Thanks! Ok, I just read about Blobs at https://developer.mozilla.org/en-US/docs/Web/API/Blob . Aside from their non-JS...
> Maybe side-stepping the problem with `Blob` is pragmatic, though there's more data copying. Perhaps implementing `Blob` with a petrified `ArrayBuffer` would allow `Blob.prototype.arrayBuffer()` to be almost free? I like...
See https://github.com/endojs/endo/pull/1538
See https://github.com/endojs/endo/pull/1171/files