/explore
|
You are here 
|
blog.ploeh.dk | ||
| | | | |
viruta.org
|
|
| | | | | ||
| | | | |
henko.net
|
|
| | | | | A deep dive into unit testing looking to answer why, how much, and what. | |
| | | | |
www.martinfowler.com
|
|
| | | | | Testing should be an integral part of programming, with automated tests providing confidence of correctness. | |
| | | | |
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. | ||
