You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to create a tracking issue corresponding to PR #1311 as the issues it resolves aren't directly about that and it would be good to have a central place to coordinate all the downstream work.
Generally IDL objects have been 1:1 with ECMAScript objects, except for
SharedArrayBuffer. That was instead represented as
[AllowShared] ArrayBuffer, although that includes ArrayBuffer as well.
This created a number of challenges, e.g., how to return a
SharedArrayBuffer object.
So we make these changes here that will also require corresponding
downstream fixes:
* SharedArrayBuffer is now its own type.
* [AllowShared] only applies to buffer view types.
* AllowSharedBufferSource takes over from [AllowShared] BufferSource.
Downstream is tracked by #1320.
Fixes#865 and fixes#961.
annevk
changed the title
Give SharedArrayBuffer a dedicated type
Give SharedArrayBuffer a dedicated type (downstream)
Jun 15, 2023
I've done everything I can at this point. At least that I know about. I'll leave this open for a bit to see if there's any other fallout and maybe wait for all downstream PRs to have landed.
I wanted to create a tracking issue corresponding to PR #1311 as the issues it resolves aren't directly about that and it would be good to have a central place to coordinate all the downstream work.
Everything under
[AllowShared]
in https://dontcallmedom.github.io/webidlpedia/extended-attributes.html is impacted:I'm pretty sure that's it, but if people think there might be more let me know.
The text was updated successfully, but these errors were encountered: