Re: [whatwg/fetch] Response constructor should handle SharedArrayBuffer (#1004)

1. I think that per IDL due to lack of `[AllowShared]` it should already throw. Firefox had a bug here that was just fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=1615741. (Not that we ship `SharedArrayBuffer` yet, but still.)
2. As shared memory is potentially dangerous, it cannot be the default and needs to be a somewhat informed and auditable decision.
3. If copy semantics are what we want here (and not sure anything else makes sense), it seems fine to add [AllowShared]` here. Probably want a more complete evaluation of the entire API surface though to see what changes to make for shared memory.

-- 
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/fetch/issues/1004#issuecomment-592918247