/explore
|
You are here 
|
iter.ca | ||
| | | | |
blog.sylver.dev
After discovering the SQLite file format and implementing the .tables command in part 1 and part 2 of this series, we're ready to tackle the next big challenge: writing our own SQL parser from scratch. As the SQL dialect supported by SQLite is quite ... |
|
| | | | | ||
| | | | |
m10k.eu
[AI summary] The author explains how to implement a recursive descent parser in Bash to define and process domain-specific language rules for selecting RPM packages. |
|
| | | | | ||
| | | | |
thume.ca
[AI summary] This blog post by Tristan Hume details his experience writing a compiler for a course project using Rust. He discusses various aspects of the project including the use of Rust's powerful enums and pattern matching, handling variable and type resolution, reference counting with Rc, code generation for x86 assembly, and the use of usercorn to run Linux binaries on macOS. The post also reflects on the challenges and benefits of using Rust for such a project, comparing it with other languages and design decisions. |
|
| | | | | ||
| | | | |
www.integralist.co.uk
I've been learning Rust recently. This will probably be my third (lazy) attempt to learn the language. The reason I've failed previously is simply because I had no reason to learn it. Other than the memory safety aspects, which I like a lot, I don't actually like the design of the language at all (but that's a conversation for another day). This time around I want to learn the language as it's pertinent to my job. |
|
| | | |||
