crash override

i know you can use reference counting or clone most everything or add GC in other ways but the entire point is not have to concern yourself with lifetimes at all until it becomes relevant. i'm thinking there's no very good reason why rust can't take the role of c, c++, and python

oh i meant the lifetime of data, not lifetime annotations. i think it's very cool that they're not needed as often but that only reduces the amount of effort needed, not the degree of understanding.

I think you can get away with not understanding of how the borrow checker works up to a point. And there is a way of nesting your data structures that comes naturally after a while of writing Rust where it's not that much of a pain anymore.

right, the more experience the less of a problem the borrow checker becomes. what would be cool is a language that you can productively use without needing a significant amount of experience.

It is a cool language that has a lot of things going for it: no hidden preprocessor macros, not being able to add side effects to the standard library, idioms like "dyn/Box/unwrap/unsafe" that can make bad code immediately stick out in code reviews

the only difference from other unmanaged languages wrt lifetime of data is that the compiler will refuse incorrect code. whether you solve that error message by adding explicit lifetimes or reference counting is up to the programmer.

right, that's the really cool thing about rust. i'm comparing it to managed languages, however, and asking whether 'gradually unmanaged rust' is viable