Explore >> Select a destination
|
You are here 
|
adam.younglogic.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. | |
| | | | |
www.abubalay.com
|
|
| | | | | [AI summary] The blog post introduces the dioptre crate, a Rust proc-macro for struct field reflection, and discusses Cell field projection techniques to enable more flexible interior mutability in Rust programs. | |
| | | | |
spacedimp.com
|
|
| | | | | ||
| | | | |
without.boats
|
|
| | | |||
