/explore
|
You are here 
|
blog.orhun.dev | ||
| | | | |
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! | |
| | | | |
mtlynch.io
|
|
| | | | | Updates about my life and what I learn about creating software | |
| | | | |
avestura.dev
|
|
| | | | | What are the problems of C, and how Zig addresses them? | |
| | | | |
blog.regehr.org
|
|
| | | [AI summary] The provided text is a discussion thread about undefined behavior in C and C++ programming languages, focusing on integer overflow, pointer aliasing, and compiler optimizations. Key points include the implications of undefined behavior in real-world code, the role of compilers in handling such cases, and the balance between adhering to standards and accommodating practical programming needs. The conversation touches on tools for detecting undefined behavior, the evolution of C/C++ standards, and the importance of unit testing and maintenance in software development. | ||
