/explore
|
You are here 
|
boats.gitlab.io | ||
| | | | |
async.rs
|
|
| | | | | ||
| | | | |
blog.polybdenum.com
I am fortunate enough to work on a production Rust service (a real one, not cryptocurrency nonsense). Rust virtually eliminates the kinds of stupid bugs and gotchas that are endemic in other languages, making it much easier to develop and maintain our project. Unfortunately, Rust is substantially less capable when it comes to preventing the common issues involved in async programming. In fact, async programming is substantially harder to get right in Rust than in something like Javascript, due to the decision to make task spawning explicit for performance reasons. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
www.ncameron.org
One of the more subtle aspects of Rust is how traits can be used as types. In this blog post I will attempt a bit of a deep dive into how to use traits as types and how to choose between the different forms. Preliminary: traits are not typesA type |
|
| | | |||
