Explore >> Select a destination
|
You are here 
|
jgayfer.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. | |
| | | | |
nora.codes
|
|
| | | | | ||
| | | | |
dehora.net
|
|
| | | | | Back in 2013, I started a series of posts on programming languages I found interesting. One of the languages I wanted to write about at that time was Rust. As often happens, life got in the way, and it's only now that I'm coming round to a long overdue post. This is one of a series of posts on programming languages and you can read more about thathere. | |
| | | | |
www.bfilipek.com
|
|
| | | Let's put C++17 in practice! One of the good ways to do it is to take part in a coding challenge. So together with Jonathan Boccara from Fluent C++ we invite you to participate in "The Expressive C++17 coding challenge". The Expressive C++17 coding challenge Jonathan made a few contests on his blog (for example this one), and I thought it might be fun to do something similar for C++17. | ||
