> 1\. I don't think thread local heaps work well for parallelism, O.k. Good, this makes things simpler. The distinction between "iso" and "trn" isn't necessary longer. "iso" does the job, and "iso" is shorter to write than "owned" isn't it. Pony strives to transfer references between threads and to maintain write-ability at the same time. It might not be a clever idea - however, Pony integrated "capabilities" in the type system. This allows some inference. Anything that can be inferred takes a burden from the programmer, makes programs shorter and reduces errors.
> Usually accessing dangling.data would be a "use after free" bug but since > dispose returns the memory to a type-safe memory pool we know that x = > Node(data: 4) will allocate memory from the same pool; either by re-using the > object that previously had the value 3 (then we know that dangling.data == 4) > or by creating a fresh object (then we know dangling.data == 3). This is exactly the pony-way with their "destructive read".
