#Rust
4 posts
Rust 1.96's Range types: taking Copy back from Iterator
Range was never Copy because it implements Iterator itself. Rust 1.96 stabilised a new family of range types that implement only IntoIterator, which makes them Copy. Why the distinction matters, and when the familiar syntax changes.
In Rust, context belongs on the line that actually fails
The question mark operator rethrows an error without saying which step failed. Structured errors in the core, Context in the application layer, with the input attached, is what makes a log line locatable.
When a crate should become a workspace
The trigger for splitting a workspace is build time and dependency boundaries, not tidy directories. Split when three signals hold, or you trade one compile for managing several packages.
Structured logging is not println replaced by tracing::info
Log lines built by concatenation can only be read by humans. Fields make them queryable. Fields, spans, levels and knowing when not to format are the four real decisions.