rename TARPL to The Rustinomicon

README.md

@@ -1,34 +1,38 @@
-% The Advanced Rust Programming Language
+% The Rustonomicon
+
+#### The Dark Arts of Advanced and Unsafe Rust Programming
 
 # NOTE: This is a draft document, and may contain serious errors
 
-So you've played around with Rust a bit. You've written a few simple programs
+> Instead of the programs I had hoped for, there came only a shuddering blackness
-and you think you grok the basics. Maybe you've even read through *[The Rust
+and ineffable loneliness; and I saw at last a fearful truth which no one had
-Programming Language][trpl]* (TRPL). Now you want to get neck-deep in all the
+ever dared to breathe before — the unwhisperable secret of secrets — The fact
-nitty-gritty details of the language. You want to know those weird corner-cases.
+that this language of stone and stridor is not a sentient perpetuation of Rust
-You want to know what the heck `unsafe` really means, and how to properly use
+as London is of Old London and Paris of Old Paris, but that it is in fact
-it. This is the book for you.
+quite unsafe, its sprawling body imperfectly embalmed and infested with queer
-
+animate things which have nothing to do with it as it was in compilation.
-To be clear, this book goes into serious detail. We're going to dig into
+
-exception-safety and pointer aliasing. We're going to talk about memory
+This book digs into all the awful details that are necessary to understand in
-models. We're even going to do some type-theory. This is stuff that you
+order to write correct Unsafe Rust programs. Due to the nature of this problem,
-absolutely don't need to know to write fast and safe Rust programs.
+it may lead to unleashing untold horrors that shatter your psyche into a billion
-You could probably close this book *right now* and still have a productive
+infinitesimal fragments of despair.
-and happy career in Rust.
+
-
+Should you wish a long and happy career of writing Rust programs, you should
-However if you intend to write unsafe code -- or just really want to dig into
+turn back now and forget you ever saw this book. It is not necessary. However
-the guts of the language -- this book contains invaluable information.
+if you intend to write unsafe code -- or just want to dig into the guts of the
-
+language -- this book contains invaluable information.
-Unlike TRPL we will be assuming considerable prior knowledge. In particular, you
+
-should be comfortable with basic systems programming and basic Rust. If you
+Unlike [The Book][trpl] we will be assuming considerable prior knowledge. In
-don't feel comfortable with these topics, you should consider [reading
+particular, you should be comfortable with basic systems programming and Rust.
-TRPL][trpl], though we will not be assuming that you have. You can skip
+If you don't feel comfortable with these topics, you should consider [reading
-straight to this book if you want; just know that we won't be explaining
+The Book][trpl] first. Though we will not be assuming that you have, and will
-everything from the ground up.
+take care to occasionally give a refresher on the basics where appropriate. You
-
+can skip straight to this book if you want; just know that we won't be
-Due to the nature of advanced Rust programming, we will be spending a lot of
+explaining everything from the ground up.
-time talking about *safety* and *guarantees*. In particular, a significant
+
-portion of the book will be dedicated to correctly writing and understanding
+To be clear, this book goes into deep detail. We're going to dig into
-Unsafe Rust.
+exception-safety, pointer aliasing, memory models, and even some type-theory.
+We will also be spending a lot of time talking about the different kinds
+of safety and guarantees.
 
 [trpl]: ../book/