Explore >> Select a destination
|
You are here 
|
ashishvegaraju.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. | |
| | | | |
blog.ploeh.dk
|
|
| | | | | In functional programming, the notion of dependencies must be rejected. Instead, applications should be composed from pure and impure functions. | |
| | | | |
danielpecos.com
|
|
| | | | | Purpose of this post is to providea glimpse of the new features included in Java 8 that shiftthis language towards a more Functional Programming paradigm. But before, let's define what we understand for Functional Programming (FP). Functional programming key characteristics include: Higher Order Functions Pure Functions and Immutability Tail Call Recursion Higher Order Functions for a FP language means that functions are considered first class citizens, allowing the programmer to use them as any other value the language defines, for example, a Function value: | |
| | | | |
poignardazur.github.io
|
|
| | | Let's talk about pinning in the Rust programming language. | ||
