/explore
|
You are here 
|
baatz.io | ||
| | | | |
limpet.net
[AI summary] This article explains Rust's memory safety guarantees by reframing the compiler's borrowing and lifetime checks as a system of unique versus shared access to data. |
|
| | | | | ||
| | | | |
thomascountz.com
Checkout Ownership in Rust, Part 1. |
|
| | | | | ||
| | | | |
manishearth.github.io
This post is now a part of the official rust book In my previous post I talked a bit about why the RWlock pattern is important for accessing data, ... |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
