mirror-github-bspeice/speice.io
1
0
Fork 0
mirror of https://github.com/bspeice/speice.io synced 2024-12-22 16:48:10 -05:00
Code Issues Releases Wiki Activity

Move the files to final resting location

Browse Source
This commit is contained in:
Bradlee Speice 2019-02-09 23:31:11 -05:00
parent 543e4253cc
commit e9099d191e
No known key found for this signature in database
GPG Key ID: 48BEA6257238E620
6 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
_drafts/understanding-allocations-in-rust.md → _posts/2019-02-04-understanding-allocations-in-rust.md
View File

@ -29,9 +29,9 @@ an understanding of the different memory types Rust makes use of, then summarize
section at the end for easy future citation. To that end, a table of contents is in order: section at the end for easy future citation. To that end, a table of contents is in order:
- Foreword - Foreword
- [The Whole World: Global Memory Usage](/2019/02/the-whole-world) - [Global Memory Usage: The Whole World](/2019/02/the-whole-world)
- [Stacking Up: Fixed Memory](/2019/02/stacking-up) - [Fixed Memory: Stacking Up](/2019/02/stacking-up)
- [A Heaping Helping: Dynamic Memory](/2019/02/a-heaping-helping) - [Dynamic Memory: A Heaping Helping](/2019/02/a-heaping-helping)
- [Compiler Optimizations: What It's Done For You Lately](/2019/02/compiler-optimizations) - [Compiler Optimizations: What It's Done For You Lately](/2019/02/compiler-optimizations)
- [Summary: What Are the Rules?](/2019/02/summary) - [Summary: What Are the Rules?](/2019/02/summary)

3
_drafts/the-whole-world.md → _posts/2019-02-05-the-whole-world.md
View File

@ -1,6 +1,6 @@
--- ---
layout: post layout: post
title: "The Whole World: Global Memory Usage" title: "Global Memory Usage: The Whole World"
description: "Static considered slightly less harmful." description: "Static considered slightly less harmful."
category: category:
tags: [rust, understanding-allocations] tags: [rust, understanding-allocations]
@ -292,4 +292,3 @@ fn main() {
} }
``` ```
-- [Rust Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=3ba003a981a7ed7400240caadd384d59) -- [Rust Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=3ba003a981a7ed7400240caadd384d59)

2
_drafts/stacking-up.md → _posts/2019-02-06-stacking-up.md
View File

@ -1,6 +1,6 @@
--- ---
layout: post layout: post
title: "Stacking Up: Fixed Memory" title: "Fixed Memory: Stacking Up"
description: "We don't need no allocator." description: "We don't need no allocator."
category: category:
tags: [rust, understanding-allocations] tags: [rust, understanding-allocations]

2
_drafts/a-heaping-helping.md → _posts/2019-02-07-a-heaping-helping.md
View File

@ -1,6 +1,6 @@
--- ---
layout: post layout: post
title: "A Heaping Helping: Dynamic Memory" title: "Dynamic Memory: A Heaping Helping"
description: "The reason Rust exists." description: "The reason Rust exists."
category: category:
tags: [rust, understanding-allocations] tags: [rust, understanding-allocations]

0
_drafts/compiler-optimizations.md → _posts/2019-02-08-compiler-optimizations.md
View File

8
_drafts/summary.md → _posts/2019-02-09-summary.md
View File

@ -37,5 +37,9 @@ the memory model in Rust:
- `const` is a fixed value; the compiler is allowed to copy it wherever useful. - `const` is a fixed value; the compiler is allowed to copy it wherever useful.
- `static` is a fixed reference; the compiler will guarantee it is unique. - `static` is a fixed reference; the compiler will guarantee it is unique.
And if you've read through both the posts and now the summary: thanks. I've enjoyed ---
the process that went into writing this, and I hope it's valuable to you as well.
And if you've read through this series: thanks. I've enjoyed the process that went
into writing this, both in building new tools and forcing myself to understand
the content well enough to explain it. I hope this is valuable as a reference to you
as well.