Use of sequential addresses for heap allocations in Stack v. Heap documentation is somewhat misleading #29853

huonw · 2015-11-16T07:09:40Z

In a typical long-running program that is performing allocations and deallocations as it goes, successive allocations are unlikely to be exactly adjacent in memory, but https://doc.rust-lang.org/stable/book/the-stack-and-the-heap.html may imply that there's more predictability than there is. That said, a normal allocator won't be completely unpredictable.

One suggestion from twitter was to use random numbers for heap allocs.

Fixes rust-lang#29853 Fixes rust-lang#29852 While these points are true, we're not going for 100% accuracy here, this is introductory material. Changing these things would be more confusing, but it is important to note that we're presenting an abstraction here.

@huonw

Fixes #29853 Fixes #29852 While these points are true, we're not going for 100% accuracy here, this is introductory material. Changing these things would be more confusing, but it is important to note that we're presenting an abstraction here. r? @huonw

huonw added the A-docs label Nov 16, 2015

steveklabnik mentioned this issue Nov 16, 2015

Reaffirm that this is an abstraction #29860

Merged

bors closed this as completed in #29860 Nov 17, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Use of sequential addresses for heap allocations in Stack v. Heap documentation is somewhat misleading #29853

Use of sequential addresses for heap allocations in Stack v. Heap documentation is somewhat misleading #29853

huonw commented Nov 16, 2015

Use of sequential addresses for heap allocations in Stack v. Heap documentation is somewhat misleading #29853

Use of sequential addresses for heap allocations in Stack v. Heap documentation is somewhat misleading #29853

Comments

huonw commented Nov 16, 2015