https://hackerpaper.kaipfister.de/p/1907.02127/Collected HN comments and submissions linking this paper.enMon, 02 Nov 2026 11:16:22 GMThttps://news.ycombinator.com/item?id=26719075urn:hackerpapers:mention:1907.02127:26719075Wed, 07 Apr 2021 00:27:03 GMT<p>Yup, NPEs are not caused in the location that they occur. They are caused by the part of the code that inserts a null where it doesn&#x27;t belong/isn&#x27;t expected. This means that getting rid of NPEs requires detailed enforcement across module/method/interface/etc boundaries. If something is labelled @Nonnull (or @NotNull, depending on the annotations used) then it should never be allowed to be null. The issue arises when there is no enforcement of this paradigm at the compiler level. Similar languages (Kotlin/Swift/...) with the benefit of Java in hindsight, can track nullability as a core…</p><p><a href="https://hackerpaper.kaipfister.de/p/1907.02127/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.SEhttps://news.ycombinator.com/item?id=20371038urn:hackerpapers:mention:1907.02127:20371038Sat, 06 Jul 2019 18:27:55 GMT<p>paper: https://arxiv.org/abs/1907.02127</p><p><a href="https://hackerpaper.kaipfister.de/p/1907.02127/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.SE