I've realized that I don't use any dependency injection in #Rust, and I don't miss it.
Cargo makes dependencies and workspaces so easy, that I break code up into small libraries instead. They are testable individually, and bigger things that would be unit tests with DI become more of integration tests instead.
thinking about the decades of pain Microsoft set themselves up for by apparently thinking they could not possibly release something called “Xbox 2” when its competitor would be a “PlayStation 3” https://www.ign.com/articles/2016/07/25/xbox-360-was-nearly-called-xbox-3-a-ign-unfiltered
The yearly state of #Rust survey is out.🎉 You can take part until the 24th of September.
Please help the Rust community improve the Rust ecosystem by taking part in the survey. It should take less than 15 minutes:
Smells Like Teen Spirit Cover In Classical Latin (75 BC to 3rd Century AD) Bardcore
Positions in #gamedev available at EmbarkStudios.
Here is the complete list:
If you're defining an alias for your crate's Result type, instead of:
type Result<T> = std::result::Result<T, MyError>;
type Result<T, E = MyError> = std::result::Result<T, E>;
This still works as `Result<()>`, but doesn't cause errors when someone accidentally shadows std's Result with it. It also makes Rustdoc display the error type explicitly in the documentation.
Do's and don'ts for #rustlang novices:
References in function arguments = do
References in structs = don't
<< it was charming when someone shortened my name to “k8e” but i am now displeased my friends (a vile pack of scoundrels) are referring to me as “kubernetelyn >>