<story><title>The Rustonomicon: The Dark Arts of Advanced and Unsafe Rust Programming</title><url>https://doc.rust-lang.org/nomicon/README.html</url></story><parent_chain><item><author>rattray</author><text>I really hope nobody mistakes the sexy title of this book as a reason to learn unsafe rust. If it can be done without this advanced feature, it probably should.</text></item></parent_chain><comment><author>vvanders</author><text>&amp;gt; However if you intend to write unsafe code -- or just want to dig into the guts of the language -- this book contains invaluable information.&lt;p&gt;Agreed, however I think the latter part of the intro is worthwhile to anyone who wants a deeper understanding of Rust.&lt;p&gt;I&amp;#x27;ve always found that a in depth understanding of what you use pays off in unforeseen ways.</text></comment>
<story><title>The Rustonomicon: The Dark Arts of Advanced and Unsafe Rust Programming</title><url>https://doc.rust-lang.org/nomicon/README.html</url></story><parent_chain><item><author>rattray</author><text>I really hope nobody mistakes the sexy title of this book as a reason to learn unsafe rust. If it can be done without this advanced feature, it probably should.</text></item></parent_chain><comment><author>bluejekyll</author><text>It&amp;#x27;s true. I have a 30k+ LoC project, and it has zero unsafe code blocks.&lt;p&gt;Though I do have another project that exports a C API, and that requires unsafe, though it&amp;#x27;s literally only for wrapping&amp;#x2F;unwrapping pointers.</text></comment>