Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.