Explore >> Select a destination
|
You are here 
|
dr-knz.net | ||
| | | | |
donsbot.com
|
|
| | | | | I've been learning Rust for the past twenty days or so, working through the Blandy & Orendorff book, coding up things as I go. Once I got into playing with Rust traits and closures and associated types, the similarities to programming in Haskell with typeclasses, data structures, closure passing and associated types was pretty obvious.... | |
| | | | |
www.evanmiller.org
|
|
| | | | | A review of Rust, the programming language built for safety - not necessarily for comfort. | |
| | | | |
www.greyblake.com
|
|
| | | | | A blog about software development. | |
| | | | |
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. | ||
