Explore >> Select a destination
|
You are here 
|
fsharpforfunandprofit.com | ||
| | | | |
jmmv.dev
|
|
| | | | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | |
| | | | |
www.parsonsmatt.org
|
|
| | | | | The question of "How do I design my application in Haskell?" comes up a lot.There's a bunch of perspectives and choices, so it makes sense that it's difficul... | |
| | | | |
blog.ploeh.dk
|
|
| | | | | In functional programming, the notion of dependencies must be rejected. Instead, applications should be composed from pure and impure functions. | |
| | | | |
njwildberger.com
|
|
| | | We are supposed to have a very clear idea about the `laws of logic'. For example, if all men are mortal, and Socrates is a man, then Socrates is mortal. Are there in factsuch things as the "laws of logic"? While we can all agree that certain rules of inference, like the example above, are... | ||
