Explore >> Select a destination
|
You are here 
|
brunosutic.com | ||
| | | | |
byroot.github.io
|
|
| | | | | I want to write a post about Pitchfork, explaining where it comes from, why it is like it is, and how I see its future. But before I can get to that, I think I need to explain a few things, namely why in many circles fork is seen as a relic of the past, if not outright the devil's creation. And yet, it's ubiquitous in the Ruby ecosystem. | |
| | | | |
noteflakes.com
|
|
| | | | | OSS Friday Update - Noteflakes | |
| | | | |
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. | |
| | | | |
thomascountz.com
|
|
| | | Checkout Ownership in Rust, Part 1. | ||
