• mmap'ing ArrayBuffers into WASM heap
• read-only ArrayBuffers and write-only(?) ArrayBuffers (that work with mmap), for buffer mapping
  • Applicability to WebGPU buffer mapping tc39/proposal-immutable-arraybuffer#25
  • WebGPU use case tc39/proposal-limited-arraybuffer#17
• ArrayBuffers (non-Shared, same thread) that point at non-disjoint ranges of the same backing data
• ArrayBuffers whose base addresses aren't maximally-aligned (e.g. Float64Array not valid at offset 0, valid at offset 4)
  • No one has asked for this yet, probably not very important
• "bitflags" equivalent functionality (e.g. Java-style EnumSet 🥺)
• Ability to make ArrayBuffers non-transferrable EDIT: It turns out this already exists as [[ArrayBufferDetachKey]]
• SharedObjectTable a bit like SharedArrayBuffer but instead of containing bytes, they contain references to shallow-cloneable objects ([Serializable] IDL interface objects). This should allow for example for GPUTextures created on one worker to be instantly visible to other workers.
  • Or (somewhat less ideal) synchronous receiveMessage() on MessagePort. (WASM multi-threading ability #476)
  • Place to draft a proposal: https://hackmd.io/@webgpu/S1f56dN8s

Please add more issues on this thread.