Hacker News Reader

I'd concur, in fact I don't know if I'd like to see the borrow checker get more complex because then it becomes harder to keep a mental model in your head of what it's doing.

I found once I grasped the model that the borrow checker uses that I rarely fight it and instead find it catching many things that I miss.

View on HN

Yes, I've said this as well. Non-lexical lifetimes will make the borrow checker more complex; but if it tends to work closer to the way that you intuit things, as a developer, it will _feel_ simpler.

Right now, the rules are very simple to explain. But that means your code gets a little more complex at times.

I think a good example of this is how value categories work in C++ (even pre-move-semantics).

It's initially quite intuitive and makes sense. But as you use the language more you start questioning why it doesn't make sense and you eventually have to learn how rvalues work.

> Right now, the rules are very simple to explain. But that means your code gets a little more complex at times.

And more awkward in places due to convincing the checker that what you're doing is ok.

Reply on news.ycombinator.com