Explore >> Select a destination
|
You are here 
|
without.boats | ||
| | | | |
asthasr.github.io
|
|
| | | | | Opinions and discussions of various topics, mostly related to programming. | |
| | | | |
smallcultfollowing.com
|
|
| | | | | ||
| | | | |
theincredibleholk.org
|
|
| | | | | As I've written about before, one of the major features we're working on adding to Rust is to allow async functions in traits. Today we have support in nightly ... | |
| | | | |
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. | ||
