Explore >> Select a destination
|
You are here 
|
aturon.github.io | ||
| | | | |
www.shuttle.dev
|
|
| | | | | All about Rust traits, generics, trait bounds and implementing advanced trait bounds | |
| | | | |
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 | |
| | | | |
purplesyringa.moe
|
|
| | | | | A few days ago, I stumbled upon a Hacker News discussion about the expression problem - a conundrum that occasionally arises in software design. Some of the commenters noted that Rust completely avoids this problem thanks to trait objects, and initially I agreed with them, but I'm now realizing it's not at all as straightforward as it looks. The goal of this post is to explain what the expression problem is, how Rust seemingly avoids it, why this solution doesn't actually work, and what a Rusty solution might look like. | |
| | | | |
aturon.github.io
|
|
| | | [AI summary] This blog post introduces Rust's zero-cost futures library, which enables efficient asynchronous I/O programming by providing high-level abstractions that compile down to low-level state-machine code without runtime overhead. | ||
