Explore >> Select a destination
|
You are here 
|
aturon.github.io | ||
| | | | |
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. | |
| | | | |
theincredibleholk.org
|
|
| | | | | As 2022 draws to a close, I want to take a moment to look at where we are with supporting async functions in dyn traits (AFIDT) and suggest some ideas for how t | |
| | | | |
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 | |
| | | | |
github.com
|
|
| | | MSVC's implementation of the C++ Standard Library. - STL/stl/inc/vector at 530bdc5aaa8a21277e1281ad3df8b8d8433b5caa · microsoft/STL | ||
