|
You are here |
nercury.github.io | ||
| | | | |
www.shuttle.rs
|
|
| | | | | Patterns to use types for better safety and design | |
| | | | |
adventures.michaelfbryan.com
|
|
| | | | | Once you get past the growing pains of the Borrow Checker and realise Rust gives you the power to do things which would be unheard of (or just plain dangerous) in other languages, the temptation to Rewrite it in Rust can be quite strong. However at best, the temptation to RiiR is unproductive (unnecessary duplication of effort), and at worst it can promote the creation of buggy software (why would you be better equipped to write a library for some domain-specific purpose than the original author? | |
| | | | |
www.shuttle.dev
|
|
| | | | | Using Huggingface with Rust | |
| | | | |
qsantos.fr
|
|
| | | Although I am now mostly comfortable with Rust, some concepts still elude me. One of them is the exact meaning of Unpin. The documentation says: The documentation of Unpin says: Types that do not require any pinning guarantees. Where pinning is described as: From this, you could naturally deduce that Unpin is the trait that ... Continue reading You can move !Unpin | ||