[peyton]

> does not prevent crashing when addressing an already released object

I don’t know what behavior you’d expect here or in what situation you’d encounter this for a nonnull reference. You’d have to be really living dangerously I’d imagine. The footgun was that nonnull isn’t enforced. And anyway, leaks were more the issue.

[catoc]

That was exactly my point.

GP mentioned ‘chasing null pointer exceptions’, then parent mentioned that the language ’now does have nonnull annotation’, prompting me to explain that that does not prevent null pointer exceptions.

So, not living a dangerously. All that can be held against me is being “dangerously” imprecise on HN - definitely not good either