MWMerlin Wellingtoninwizardcraftcode.hashnode.dev·Jul 1 · 7 min readWhat a Proliferation of Clones is Trying to Tell You About Your Rust APIWhen you are fighting the Rust borrow checker, it can easily feel like the compiler is actively getting in your way. You hit a brick wall with error[E0382]: use of moved value, and then you remember t00
MWMerlin Wellingtoninwizardcraftcode.hashnode.dev·Jun 26 · 5 min readStop Forcing Classes Into Rust: Methods vs. Free FunctionsIf you learned to program in an object-oriented language, you were taught that data and the functions that operate on that data belong together—bound forever inside a class framework. When you come to00
MWMerlin Wellingtoninwizardcraftcode.hashnode.dev·Jun 17 · 3 min readYour Getters are Ruining Your Rust CodeComing to Rust from object-oriented languages like Java, C++, or C# creates a dangerous form of muscle memory. In the object-oriented paradigm, encapsulation dictates a simple rule: hide your struct f00
MWMerlin Wellingtoninwizardcraftcode.hashnode.dev·Jun 10 · 6 min readHow to Design Rust Ownership (Without the Guesswork)We have all been there. You are writing a fresh Rust feature, you get a flash of inspiration, and you type out fifty lines of complex logic. You hit save, run the compiler, and get hit with a wall of 00
MWMerlin Wellingtoninwizardcraftcode.hashnode.dev·Jun 8 · 4 min readThe Sigil Framework: A Visual Reference for Rust Ownership & BorrowingIf you are coming to Rust from languages with a garbage collector (like Go, Java, or JavaScript) or manual memory management (like C++), Rust's ownership model can feel like an arbitrary set of syntax10
