Programming languages without garbage collection send us down a long path of design decisions that lead to slow compile times and fragile runtime performance cliffs.
-
-
And that only works in function call chains. If you're trying to store a vector<byte> in a heap variable of type vector<int>, either you have to convert it all, or reference it and be deeply aware of the lifetime relationships between the two things. Which GC solves.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It seems orthogonal to me. If you want a typed view into the original vector, you need the lifetime to match - but it doesn’t seem too different from passing a reference to a vector to some other system without any type conversions?
-
What all of these subtyping-through-zero-copy-sharing-through-manual-memory-management solutions have in common is that, in a large program, the combinatorial complexity of all of these lifetime relationships is impossible for a human to comprehend. Thus libraries don't do it.
- 14 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.