Explore >> Select a destination
|
You are here 
|
blog.burntsushi.net | ||
| | | | |
www.fosskers.ca
|
|
| | | | | ||
| | | | |
nick.groenen.me
|
|
| | | | | After working through "the book" on the Rust programming language and getting started with the first non-trivial, real-world application I found myself faced with a question I didn't yet feel well-equipped to handle: "How should you structure error handling in a mature rust application?" | |
| | | | |
blog.m-ou.se
|
|
| | | | | The fmt::Arguments type is one of my favorite types in the Rust standard library. It's not particularly amazing, but it is a great building block that is indirectly used in nearly every Rust program. This type, together with the format_args!() macro, is the power behind print!(), format!(), log::info!() and many more text formatting macros, both from the standard library and community crates. In this blog post, we learn how it works, how it is implemented today, and how that might change in the future. | |
| | | | |
boats.gitlab.io
|
|
| | | Today I realized a new crate called pin-cell. This crate contains a type called PinCell, which is a kind of cell that is similar to RefCell, but only can allow pinned mutable references into its interior. Right now, the crate is nightly only and no-std compatible. How is the API of PinCell different from RefCell? When you call borrow_mut on a RefCell, you get a type back that implements DerefMut, allowing you to mutate the interior value. | ||
