/explore
|
You are here 
|
blog.lohr.dev | ||
| | | | |
www.abubalay.com
[AI summary] This post discusses the complexities of creating safe Foreign Function Interface (FFI) bindings in Rust when calling C++ code, examining tools like cxx and strategies for maintaining Rust's memory and thread-safety guarantees despite the inherent unsafety in such interactions. |
|
| | | | | ||
| | | | |
dehora.net
Back in 2013, I started a series of posts on programming languages I found interesting. One of the languages I wanted to write about at that time was Rust. As often happens, life got in the way, and it's only now that I'm coming round to a long overdue post. This is one of a series of posts on programming languages and you can read more about thathere. |
|
| | | | | ||
| | | | |
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! |
|
| | | | | ||
| | | | |
manishearth.github.io
Edit (Jan 2017): I re-discovered Niko's post which touches on this and reaches for the same realization. I suspect I subconsciously got the idea for ... |
|
| | | |||
