mirror-github-bspeice/speice.io
1
0
Fork 0
mirror of https://github.com/bspeice/speice.io synced 2024-11-05 01:28:09 -05:00
Code Issues Releases Wiki Activity

More drafting ideas

Browse Source
This commit is contained in:
Bradlee Speice 2018-12-19 22:21:54 -06:00
parent 43845d8e38
commit b0fe32c4dc
1 changed files with 29 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
_drafts/understanding-allocations-in-rust.md
View File

@ -36,4 +36,32 @@ to assist in easy navigation:
- Understanding Compiler Optimizations
- Summary: When does Rust allocate?
# Distinguishing regions of memory
# Distinguishing regions of memory
# Rust and the Stack
Example: Why doesn't `Vec::new()` go to the allocator?
Questions:
1. What is the "Push" instruction? Why do we like the stack?
2. How does Rust allocate arguments to the function?
3. How does Rust allocate variables created in the function but never returned?
4. How does Rust allocate variables created in the function and returned?
5. How do Option<> or Result<> affect structs?
6. How are arrays allocated?
7. Legal to pass an array as an argument?
# Rust and the Heap
Example: How to trigger a heap allocation
Questions:
1. Where do collection types allocate memory?
2. Does a Box<> always allocate heap?
3. Passing Box<Trait> vs. genericizing/monomorphization
# Understanding compiler optimizations
Example: Compiler stripping out allocations of Box<>, Vec::push()