Explore >> Select a destination
|
You are here 
|
blog.luizirber.org | ||
| | | | |
www.trickster.dev
|
|
| | | | | Code level discussion of web scraping, gray hat automation, growth hacking and bounty hunting | |
| | | | |
paulbutler.org
|
|
| | | | | ||
| | | | |
blog.nodraak.fr
|
|
| | | | | In this article, I would like to talk about two technologies I've been playing with recently: the Rust programming language and the WebAssembly standard. I'll start by presenting each of these two technologies and which problems they are trying to solve. Then, I'll explain what are the advantages of a Rust-powered Wasm module, and why it can be useful. Finally, I'll provide links to interesting documentation. WebAssembly Since many years, client side web applications, implemented in JavaScript, have been becoming larger and larger. | |
| | | | |
dusty.phillips.codes
|
|
| | | In earlier articles, we have implemented a tokenizer, parser, and transformer to convert the Web Assembly Text Format to an Abstract Syntax Tree that can hopefully easily compile to Wasm. Truthfully, the next step should be validation. Validation is the process of statically analyzing the syntax tree to catch as many errors as possible. This is where things like type checking and borrow checking happen, for example. The wasm spec has an in-depth description of what validation should look like for a conforming compiler. | ||
