> There's also a somewhat newer Rust-like ownership + borrow-checker system in D, with @live. > > https://dlang.org/blog/2019/07/15/ownership-and-borrowing-in h

> There's also a somewhat newer Rust-like ownership + borrow-checker system in D, with @live. > > https://dlang.org/blog/2019/07/15/ownership-and-borrowing-in https://dlang.org/blog/2019/07/15/ownership-and-borrowing-in... > > https://news.ycombinator.com/item?id=20441519 https://news.ycombinator.com/item?id=20441519 I'm really annoyed when people repeat the part about D having a Rust-like borrow checking system. This is absolutely something that the project has communicated about, but that communication shouldn't be repeated uncritically. If you actually look at what @live semantics are like... well, they're quite incomplete, under-specified, and they lack a roadmap for getting to a state where they could offer GC-less memory safety in D. I have yet to hear of any project successfully using the @live feature in a production environment, and I fully expect the same thing to be true 5 years from now. D's @live is a mirage.