Re: [heycam/webidl] Idea for [AllowShared] (handling SharedArrayBuffer safely) (#638)

> I was thinking that if it happens as the last step of conversion

For that one argument, or for all arguments?  That is, is it a step added to https://heycam.github.io/webidl/#es-to-object or is it a step added to https://heycam.github.io/webidl/#es-operations after step 2.1.5?

In the former case, it can only be optimized out if the thing you're dealing with is the "last argument" or something.

In the latter case, implementing it is pretty complicated (think `sequence<SomeDictionaryType>` where the dictionary contains a member of type `record<USVString, sequence<object>>` or something).

>    * Making it easier to audit places where SharedArrayBuffer is used.

OK.  Doing this on the spec level is a bit of a pain, I agree.  Doing it on the code level in browsers is not too bad.  For Firefox, say, you'd look at https://searchfox.org/mozilla-central/search?q=symbol:_ZNK7mozilla3dom15TypedArray_base15DataAllowSharedEv&redirect=false and https://searchfox.org/mozilla-central/search?q=IsSharedArrayBuffer&case=true and probably https://searchfox.org/mozilla-central/search?q=symbol:_Z26JS_GetTypedArraySharednessP8JSObject&redirect=false

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/638#issuecomment-460696253