Search results

Memory Sharing Discussion

Status: Open.

#19 In WebAssembly/memory-control;

· woodsmc opened on Dec 6, 2024

Sub-proposal: <code>virtual</code> mode

Status: Open.

#18 In WebAssembly/memory-control;

· bvisness opened on Aug 16, 2024

Sub-proposal: <code>maplength</code>

Status: Open.

#17 In WebAssembly/memory-control;

· bvisness opened on Aug 16, 2024

Sub-proposal: static memory protection

Status: Open.

#16 In WebAssembly/memory-control;

· bvisness opened on Aug 16, 2024

Sub-proposal: BYOB for WebAssembly.Memory

Status: Open.

#15 In WebAssembly/memory-control;

· bvisness opened on Aug 16, 2024

Reducing copies by using streams

Status: Open.

#13 In WebAssembly/memory-control;

· bvisness opened on May 31, 2024

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

Status: Open.

#11 In WebAssembly/memory-control;

· dtig opened on May 22, 2024

<code>memory.discard</code> in a separate proposal?

Status: Open.

#7 In WebAssembly/memory-control;

· llenotre opened on Aug 16, 2023

Sub-proposal: <code>memory.discard</code>

Status: Open.

#6 In WebAssembly/memory-control;

· bvisness opened on Feb 15, 2023

The old memory mapping ringbuffer trick use-case

Status: Open.

#5 In WebAssembly/memory-control;

· Daniel-Abrecht opened on Jan 16, 2023

Suggestion: mappable memories

Status: Open.

#4 In WebAssembly/memory-control;

· dead-claudia opened on Nov 1, 2022

Story for refs?

Status: Open.

#3 In WebAssembly/memory-control;

· dead-claudia opened on Nov 1, 2022