Explore >> Select a destination
|
You are here 
|
danluu.com | ||
| | | | |
travisdowns.github.io
|
|
| | | | | Probing a previously undocumented zero-related optimization on Intel CPUs. | |
| | | | |
halobates.de
|
|
| | | | | Tilting at windmills and other endeavors | |
| | | | |
mechanical-sympathy.blogspot.com
|
|
| | | | | When trying to build a highly scalable system the single biggest limitation on scalability is having multiple writers contend for any item o... | |
| | | | |
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. | ||
