Skip to content

Add discussion about a max-memory-address-accessed hint alternative to the overview document#12

Merged
fitzgen merged 1 commit into
mainfrom
max-memory-address-accessed-hint
Apr 30, 2024
Merged

Add discussion about a max-memory-address-accessed hint alternative to the overview document#12
fitzgen merged 1 commit into
mainfrom
max-memory-address-accessed-hint

Conversation

@fitzgen

@fitzgen fitzgen commented Apr 25, 2024

Copy link
Copy Markdown
Collaborator

This alternative approach was briefly discussed (and withdrawn) during the last CG meeting. The new text introduced in this commit expands on the discussion from the CG meeting and describes the advantages that allowing customization of the Wasm page size has over such a max-memory-address-accessed hint.

This alternative approach was briefly discussed (and withdrawn) during the last
CG meeting. The new text introduced in this commit expands on the discussion
from the CG meeting and describes the advantages that allowing customization of
the Wasm page size has over such a max-memory-address-accessed hint.
@fitzgen

fitzgen commented Apr 30, 2024

Copy link
Copy Markdown
Collaborator Author

Okay, its been a few days, I'm going to go ahead and merge this one.

@fitzgen
fitzgen merged commit e3b15b5 into main Apr 30, 2024
@fitzgen
fitzgen deleted the max-memory-address-accessed-hint branch April 30, 2024 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant