[Parser] Support inline data in 64-bit memory declarations #6364
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
| Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
kripken approved these changes Feb 29, 2024
tlively force-pushed the parser-data-64 branch from cbd7250 to 49b1f36 Compare 
This new form of the abbreviated memory declaration with inline data is introduced in the memory64 proposal.
tlively force-pushed the parser-data-64 branch from 49b1f36 to 79b3a97 Compare 
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
This new form of the abbreviated memory declaration with inline data is
introduced in the memory64 proposal.