Explore >> Select a destination
|
You are here 
|
corrode.dev | ||
| | | | |
borretti.me
|
|
| | | | | Reflections on using Rust professionally for two years. | |
| | | | |
sakurakat.systems
|
|
| | | | | Rust's v1.0 hit 10 year mark recently so I wanted to write about why I like, and prefer Rust over the other languages I've tried. The fact of the matter is that Rust's memory safety plays a smaller role than you'd expect. | |
| | | | |
andreabergia.com
|
|
| | | | | This post is part of the Languages Opinion series. Languages opinion - part one - JVM Languages opinion - part two - Rust ??thispost Languages opinion - part three - Javascript and Typescript Welcome back to my mini-series about programming languages. In this post, we will talk about one of the most interesting programming languages that I have seen in a long while: Rust. | |
| | | | |
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. | ||
