Explore >> Select a destination
|
You are here 
|
fsharpforfunandprofit.com | ||
| | | | |
blog.ploeh.dk
|
|
| | | | | In functional programming, the notion of dependencies must be rejected. Instead, applications should be composed from pure and impure functions. | |
| | | | |
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.bartoszsypytkowski.com
|
|
| | | | | Today, we're going to cover different ways of encapsulating capabilities and supplying them between functions using functional programming techniques which can be realized in F#. Managing code dependencies in object oriented languages in 2020 is pretty much one sided problem: dependency injection has won, people use dedicated frameworks to handle | |
| | | | |
laihoconsulting.com
|
|
| | | Website and personal blog of Pekka Laiho, software engineer and financial enthusiast. | ||
