<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oxide: The Essence of Rust · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1903.00982/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1903.00982/feed.xml" rel="self" type="application/rss+xml" /><item><title>Oxide: The Essence of Rust — mentioned by j-pb</title><link>https://news.ycombinator.com/item?id=29112357</link><guid isPermaLink="false">urn:hackerpapers:mention:1903.00982:29112357</guid><pubDate>Thu, 04 Nov 2021 20:46:44 GMT</pubDate><description>&lt;p&gt;The shallowness of rusts correctness has pretty much killed my interest in it. Much of its purported virtue seems to be mostly lore and myth, and doesn&amp;#x27;t keep its promises under close inspection and scrutiny. For example the &amp;quot;Rustonomicon&amp;quot; is only half finished and doesn&amp;#x27;t have that much real insight that couldn&amp;#x27;t be gained from a lot of basic-ish rust tutorials. The memory model is not propery defined and only kinda sorta borrowed from C++ as the article mentions. The borrow checker has only been formally specified and veryfied in a much simplified form and only very recently [2] ,with the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1903.00982/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Oxide: The Essence of Rust — mentioned by j-pb</title><link>https://news.ycombinator.com/item?id=28698606</link><guid isPermaLink="false">urn:hackerpapers:mention:1903.00982:28698606</guid><pubDate>Wed, 29 Sep 2021 19:24:52 GMT</pubDate><description>&lt;p&gt;When you push a package to crates.io, docs.rs will do a static analysis of this package and its dependencies and try its best to create meaningful links between the traits and implementing types. The issue is that it is quite common to have trait definitions in one create being used by other ones. Often this is even done when a single library gets too large e.g. tokio, one incentive for splitting being compile time. However since analysis happens upwards the dependency tree, nodes further up the chain won&amp;#x27;t know what&amp;#x27;s below them and can&amp;#x27;t link to them. You&amp;#x27;d essentially have to do whole…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1903.00982/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Oxide: The Essence of Rust — HN submission</title><link>https://news.ycombinator.com/item?id=27164131</link><guid isPermaLink="false">urn:hackerpapers:submission:1903.00982:27164131</guid><pubDate>Sat, 15 May 2021 10:56:30 GMT</pubDate><description>&lt;p&gt;Oxide: The Essence of Rust (2020)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;76 points; 13 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1903.00982/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Oxide: The Essence of Rust — HN submission</title><link>https://news.ycombinator.com/item?id=19310950</link><guid isPermaLink="false">urn:hackerpapers:submission:1903.00982:19310950</guid><pubDate>Tue, 05 Mar 2019 15:06:22 GMT</pubDate><description>&lt;p&gt;Oxide: A Formal Semantics for Rust&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;223 points; 30 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1903.00982/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Oxide: The Essence of Rust — mentioned by ktpsns</title><link>https://news.ycombinator.com/item?id=19310027</link><guid isPermaLink="false">urn:hackerpapers:mention:1903.00982:19310027</guid><pubDate>Tue, 05 Mar 2019 12:18:05 GMT</pubDate><description>&lt;p&gt;Obviously https://arxiv.org/abs/1903.00982 was meant.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1903.00982/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
