diff options
author | Josh Lee <jleedev@gmail.com> | 2019-05-22 08:51:34 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-05-22 08:51:34 -0400 |
commit | 1eff6fdab5aaf641c273f08a778db1e1c9d50f30 (patch) | |
tree | ca24bd08ba54ec6c68fdf06ffd96b34b77eedfae /content | |
parent | 399010a0b4c68efe94b6e6b0bf36602804f74ee4 (diff) |
markdown typo fix
Diffstat (limited to 'content')
-rw-r--r-- | content/2019-05-21-this-week-in-rust.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/2019-05-21-this-week-in-rust.md b/content/2019-05-21-this-week-in-rust.md index a08cd76..31e210b 100644 --- a/content/2019-05-21-this-week-in-rust.md +++ b/content/2019-05-21-this-week-in-rust.md @@ -159,7 +159,7 @@ Email the [Rust Community Team][community] for access. # Quote of the Week -> Just the presence of well integrated Algebraic Data Types (ADTs) makes an incredible amount of difference. They are used to represent errors in a meaningful and easy to understand way (`Result<T>`), are used to show that a function may or may not return a meaningful value without needing a garbage value (`Option<T>`), and the optional case can even be used to wrap a null pointer scenario in a safe way (Option<Ref<T>> being the closest to a literal translation I think). +> Just the presence of well integrated Algebraic Data Types (ADTs) makes an incredible amount of difference. They are used to represent errors in a meaningful and easy to understand way (`Result<T>`), are used to show that a function may or may not return a meaningful value without needing a garbage value (`Option<T>`), and the optional case can even be used to wrap a null pointer scenario in a safe way (`Option<Ref<T>>` being the closest to a literal translation I think). > > That’s just one small feature that permeates the language. Whatever the opposite of a death-of-a-thousand-cuts is, Rust has it. |