- From: <bugzilla@jessica.w3.org>
- Date: Thu, 21 Jan 2016 23:10:10 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29388
Bug ID: 29388
Summary: Attribute to prevent calls to function passing
TypedArray w/ backing SharedArrayBuffer
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: WebIDL
Assignee: cam@mcc.id.au
Reporter: binji@chromium.org
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-script-coord@w3.org
Target Milestone: ---
SharedArrayBuffers are a new spec that is being proposed for JavaScript. See
the spec here: http://lars-t-hansen.github.io/ecmascript_sharedmem/shmem.html
They use the same TypedArray hierarchy, but they will have a backing store that
can be shared between Workers.
It's likely that most APIs will not want to allow TypedArrays with a backing
SharedArrayBuffer to be passed, and instead to throw an exception.
I sent a message to blink-dev asking about this (see
https://groups.google.com/a/chromium.org/d/topic/blink-dev/EsX3S43nm-0/discussion)
and they suggested communicating with the WebIDL authors.
My initial thought is that passing shared TypedArrays should be opt-in, so by
default they will throw an exception. The APIs that want to accept a shared
TypedArray will be annotated in some way (per function? per function argument?)
Does this seem reasonable?
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 21 January 2016 23:10:12 UTC