/explore
|
You are here 
|
josiahparry.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. |
|
| | | | | ||
| | | | |
hoverbear.org
A computer scientist working in open source towards a more hopeful future. |
|
| | | | | ||
| | | | |
r-spatial.github.io
Convert foreign object to an sf object |
|
| | | | | ||
| | | | |
fharrell.com
[AI summary] This post by Frank Harrell explores how to translate a compound symmetric correlation structure in longitudinal data into first- and fifth-order Markov model semiparametric regression approaches, and examines how including lagged variables affects random effects in a Bayesian mixed model. |
|
| | | |||
