Explore >> Select a destination
|
You are here 
|
tmandry.gitlab.io | ||
| | | | |
without.boats
|
|
| | | | | [AI summary] A deep dive into the design challenges of asynchronous clean-up in Rust and a proposal combining async cancellation and 'do...final' blocks to solve them. | |
| | | | |
blog.yoshuawuyts.com
|
|
| | | | | ||
| | | | |
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. | |
| | | | |
www.iroh.computer
|
|
| | | Documenting some painful lessons we learned while writing iroh using async Rust | ||
