diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-01-23 14:13:32 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-01-23 14:16:48 -0800 |
commit | ee67a3417802a66e2d8741536dedf99baf78cc5a (patch) | |
tree | 86560ac5e7da6b461b2dd16b5b4b7fdd67843aa2 /sandbox | |
parent | cf478e14aab32fbfcccd7443e6b2de4f2c247060 (diff) | |
download | mu-ee67a3417802a66e2d8741536dedf99baf78cc5a.tar.gz |
2596 - experiment: no unique addresses in calls
Reading http://www.jonathanturner.org/2016/01/rust-and-blub-paradox.html, I realize there's nothing currently stopping mu programs from taking a unique (non-shared) address into a shared allocation, abandoning the allocation and being left with an invalid address. No fix for this yet, but let's try to minimize its effect by limiting lifetimes of unique addresses. We really should only be using them to write to array or container elements.
Diffstat (limited to 'sandbox')
0 files changed, 0 insertions, 0 deletions