Explore >> Select a destination
|
You are here 
|
blog.thea.codes | ||
| | | | |
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. | |
| | | | |
stribny.name
|
|
| | | | | A complete guide to testing Python applications with Pytest, pytest plugins and other test libraries. | |
| | | | |
doughellmann.com
|
|
| | | | | ||
| | | | |
zackoverflow.dev
|
|
| | | Interfaces rely on slow dynamic-dispatch, but generics could open the door to performance boosts with the ability to leverage the cache-friendliness of static dispatch | ||
