WebAssembly/memory-control

Issues

• Sub-proposal: `virtual` mode

  #18 opened 3 months ago by bvisness
  4

• Sub-proposal: `maplength`

  #17 opened 3 months ago by bvisness
  0

• Sub-proposal: static memory protection

  #16 opened 3 months ago by bvisness
  0

• Sub-proposal: `memory.discard`

  #6 opened 2 years ago by bvisness
  4

• Sub-proposal: BYOB for WebAssembly.Memory

  #15 opened 3 months ago by bvisness
  0

• wasi-webgpu want this, let's moving this forward

  #9 opened 3 months ago by lygstate
  1

• Reducing copies by using streams

  #13 opened 5 months ago by bvisness
  0

• Memory mapping: Using a single linear memory + requirements discussion

  #8 opened 5 months ago by dtig
  2

• What should happen on memory.unmap? Should a subsequent memory access trap?

  #11 opened 6 months ago by dtig
  5

• Suggestion: mappable memories

  #4 opened 2 years ago by dead-claudia
  7

• `memory.discard` in a separate proposal?

  #7 opened a year ago by llenotre
  7

• `mlock`

  #1 opened 3 years ago by daxpedda
  3

• The old memory mapping ringbuffer trick use-case

  #5 opened 2 years ago by Daniel-Abrecht
  0

• Story for refs?

  #3 opened 2 years ago by dead-claudia
  2

• When this be present in https://github.com/WebAssembly/proposals

  #2 opened 3 years ago by lygstate
  1