|
You are here |
www.schneems.com | ||
| | | | |
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. | |
| | | | |
coredumped.dev
|
|
| | | | | Updated: 2023-01-06 About a year ago I was bitten by the PL bug. It started with reading Crafting Interpreters and discovering the wonders hidden under the hood of a compiler. I am also been a big fan of Emacs, and this started to get me interested in how its interpreter works. At the same time, I was reading the Rust book and trying to understand the concepts there. This all came to a head, and I decided to write an Emacs Lisp interpreter called rune in Rust. | |
| | | | |
corrode.dev
|
|
| | | | | Programming is an iterative process. As much as we would like to come up with the perfect solution from the start, it rarely works that way. Good programs often begin as quick prototypes. While many experiments remain prototypes, the best p... | |
| | | | |
nora.codes
|
|
| | | [AI summary] The article explains the concept of 'unsafe' in Rust, clarifying that it allows specific low-level operations while maintaining overall memory safety through the language's type system and safe abstractions. | ||