4 ms·
If this is referring to the proposed C++ lifetime profile, it seems as though recently it has scaled back its ambitions from detecting all misuses of references
by kibwen 8y ago
If this is referring to the proposed C++ lifetime profile, it seems as though recently it has scaled back its ambitions from detecting all misuses of references to now detecting only common misuses of references. Still useful for C++ programmers, certainly, but it's no longer really comparable to Rust's borrow checker. And even with it, it's not going to change anyone from using an ECS to using a reference scheme; the point is that references aren't the best pointer abstraction for these sorts of thoroughly-dynamic graphs with elements of dynamic lifetime.
- pjmlp 8y agoYes I am referring to that proposal, as for ECS, indexes are not a must. https://www.gamedev.net/blogs/entry/2265481-oop-is-dead-long-live-oop/ https://www.gamedev.net/blogs/entry/2265481-oop-is-dead-long... In this particular case, currently Rust's borrow checker isn't of much help either, hence the workaround with generations.