> Single ownership with a back reference is a very common need, and it's too hard to do. I've been collecting a list[1] of what memory-management policies prog

> Single ownership with a back reference is a very common need, and it's too hard to do. I've been collecting a list[1] of what memory-management policies programmers actually want in their code; it is far more extensive than any particular language actually implements. Contributions are welcome! I already had back reference on the list, but added some details. When the ownership is indirect (really common) it is difficult to automate. One thing that always irritates me: Rust's decision to make all objects moveable really hurts it at times. [1] https://gist.github.com/o11c/dee52f11428b3d70914c4ed5652d43f7 https://gist.github.com/o11c/dee52f11428b3d70914c4ed5652d43f...