Fix link to WASM Custom Section #90
Merged
Conversation
This file contains 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
|
Yep, seems like. Thank you for the update |
|
Actually it looks like maybe the binary format was moved to https://webassembly.github.io/spec/core/binary/modules.html#custom-section |
JSMonk
reviewed
Jun 11, 2024
JSMonk
approved these changes
Jun 11, 2024
JSMonk
reviewed
Jun 11, 2024
nicolo-ribaudo
approved these changes
Jun 11, 2024
github-actions bot
added a commit
that referenced
this pull request
Jun 11, 2024
SHA: 47b859a Reason: push, by jkup Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot
added a commit
to nicolo-ribaudo/source-map
that referenced
this pull request
Jun 12, 2024
SHA: 47b859a Reason: push, by nicolo-ribaudo Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@JSMonk it looks like the w3 link we have is no longer working, is this the one we should be using?