Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/sunfishcode/wasm-reference-manual
WebAssembly Reference Manual
https://github.com/sunfishcode/wasm-reference-manual
Last synced: 27 days ago
JSON representation
WebAssembly Reference Manual
- Host: GitHub
- URL: https://github.com/sunfishcode/wasm-reference-manual
- Owner: sunfishcode
- License: apache-2.0
- Created: 2016-09-04T16:45:47.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2023-01-26T21:48:51.000Z (almost 2 years ago)
- Last Synced: 2024-10-06T02:16:05.799Z (about 1 month ago)
- Homepage: https://github.com/sunfishcode/wasm-reference-manual/blob/master/WebAssembly.md
- Size: 271 KB
- Stars: 592
- Watchers: 30
- Forks: 75
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-list - wasm-reference-manual
README
# WebAssembly Reference Manual
This project contains a [human-readable WebAssembly reference manual document written in Markdown](https://github.com/sunfishcode/wasm-reference-manual/tree/master/WebAssembly.md). It is intended as an alternative to the [official WebAssembly specification](https://webassembly.github.io/spec/), which is organized around a particular approach to language specification, rather than on explanation. If you want to know how the WebAssembly runtime works, are writing a compiler, or want to try writing WebAssembly by hand (in text format), this manual is a good starting point.
## Contribution
This is not the official WebAssembly specification, and as a result, will not be updated by the W3C working group as the specification evolves. For that reason, contributions are most welcome.
This work is public domain, and distributed under the CC0 1.0 Universal licence.
## Current issues
Github-flavored Markdown is almost just powerful enough for this use case; the main things it lacks are automatic tables of contents and convenient term definitions, however the advantages in simplicity and convenient workflows partly make up for that.
Known deficiencies are marked with TODO comments. Corrections and contributions are welcome!