/explore
|
You are here 
|
kristoff.it | ||
| | | | |
andrewkelley.me
|
|
| | | | | [AI summary] The blog post discusses the evolution of programming languages, focusing on Rust and Zig's approaches to handling formatted output. It highlights the challenges in C's format string system, the use of macros in Rust, and Zig's ability to handle formatted output without special compiler cases, relying on userland code. The post also touches on the trade-offs of macros and the design goals of Zig to provide power without the drawbacks of macro-based systems. | |
| | | | |
mrcat.au
|
|
| | | | | I've started learning Zig, a new programming language in the same problem space as C, and it has some features I really like. While it's not memory-safe in the Rust way, it has a lot of compile time and runtime checks to prevent common footguns. It has packed structs and variable-width integers to allow for easy parsing of bitpacked binary formats. Its comptime metaprogramming capabilities are spectacular. And it even interoperates seamlessly with C! | |
| | | | |
ciesie.com
|
|
| | | | | Today I've played around with Zig, the new, hip (is it hip?) programming language. I find it pretty neat. I'm going to walk you (and myself) through my first, very short, piece of code. Below you can see the entirety of it. It basically allocates a 2MB buffer and reads a file into it... Yep, not particularly impressive, but this is a judgment free, learning zone, ok?! 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 const std = @import("std"); const warn = @import("std"). | |
| | | | |
limpet.net
|
|
| | | [AI summary] This article explains Rust's memory safety guarantees by reframing the compiler's borrowing and lifetime checks as a system of unique versus shared access to data. | ||
