Explore >> Select a destination
|
You are here 
|
gist.github.com | ||
| | | | |
os.phil-opp.com
|
|
| | | | | In this post, we explore cooperative multitasking and the async/await feature of Rust. We take a detailed look at how async/await works in Rust, inclu | |
| | | | |
sabrinajewson.org
|
|
| | | | | The main focus of this article will be on attempting to design a system to support asynchronous destructors in the Rust programming language, figuring the exact semantics of them and resolving any issues encountered along the way. By side effect, it also designs a language feature called async genericity which enables supporting blocking and asynchronous code with the same codebase, as well as designing a system for completion-guaranteed futures to be added to the language. | |
| | | | |
without.boats
|
|
| | | | | ||
| | | | |
jmmv.dev
|
|
| | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | ||
