/explore
|
You are here 
|
blog.weiznich.de | ||
| | | | |
smallcultfollowing.com
|
|
| | | | | [AI summary] A developer explains the technical challenges of ensuring async trait functions return Send futures in Rust and proposes a syntax solution where function callers specify send requirements rather than enforcing them globally in the trait definition. | |
| | | | |
hackmd.io
|
|
| | | | | Why aren't they just | |
| | | | |
theincredibleholk.org
|
|
| | | | | As I've written about before, one of the major features we're working on adding to Rust is to allow async functions in traits. Today we have support in nightly ... | |
| | | | |
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! | ||
