https://hackerpaper.kaipfister.de/p/1804.10806/Collected HN comments and submissions linking this paper.enMon, 02 Nov 2026 11:16:22 GMThttps://news.ycombinator.com/item?id=30831811urn:hackerpapers:mention:1804.10806:30831811Mon, 28 Mar 2022 15:52:00 GMT<p>Surely the first step should be to push the language and formalize a spec first? Example of a beginning effort: &quot;KRust: A Formal Executable Semantics of Rust&quot;&#x27; https://arxiv.org/abs/1804.10806</p><p><a href="https://hackerpaper.kaipfister.de/p/1804.10806/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.PLhttps://news.ycombinator.com/item?id=16970050urn:hackerpapers:submission:1804.10806:16970050Tue, 01 May 2018 18:42:21 GMT<p>KRust: A Formal Executable Semantics of Rust</p><p></p><p>148 points; 48 discussion replies on HN. <a href="https://hackerpaper.kaipfister.de/p/1804.10806/">Paper and source history</a>. A submission is not an endorsement.</p>cs.PLhttps://news.ycombinator.com/item?id=16965151urn:hackerpapers:submission:1804.10806:16965151Tue, 01 May 2018 07:21:26 GMT<p>KRust: A Formal Executable Semantics of Rust</p><p></p><p>4 points; 0 discussion replies on HN. <a href="https://hackerpaper.kaipfister.de/p/1804.10806/">Paper and source history</a>. A submission is not an endorsement.</p>cs.PL