Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Memories Proposal Support #21

Merged
merged 2 commits into from
Jul 30, 2024
Merged

Conversation

CharlieTap
Copy link
Owner

The multiple memories proposal recently moved to Stage 5 alongside the GC proposal and others, in order to maintain compatibility with latest spec I have implemented the proposal.

The multiple memories proposal is largely the removal of a restriction as opposed to entirely new behaviour. Instances are now able to address more than one memory, be it imported or described in the module itself. Theres a number of advantages to this and particularly this will play nice with the threads proposal, where memories can be marked as shared and concurrently accessed from different module instances. Without multiple memories all memory operations would need to be atomic to be safe, whereas with this proposal a separate memory can be constructed for shared thread communication.

@CharlieTap CharlieTap merged commit 0e2b613 into main Jul 30, 2024
3 checks passed
@CharlieTap CharlieTap deleted the proposal/multiple-memories branch July 30, 2024 20:32
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