<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Usability of Advanced Type Systems: Rust as a Case Study · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2301.02308/</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/2301.02308/feed.xml" rel="self" type="application/rss+xml" /><item><title>The Usability of Advanced Type Systems: Rust as a Case Study — mentioned by DylanSp</title><link>https://news.ycombinator.com/item?id=35334691</link><guid isPermaLink="false">urn:hackerpapers:mention:2301.02308:35334691</guid><pubDate>Tue, 28 Mar 2023 01:35:23 GMT</pubDate><description>&lt;p&gt;Interesting that this came up; I was reading https://arxiv.org/abs/2301.02308, on Rust&amp;#x27;s usability, earlier today. One of the interesting conclusions from that paper was that while Rust&amp;#x27;s error messages are generally high-quality, they can sometimes be too local, especially for helping get new Rust programmers used to the ownership model. Key quote: &amp;quot;rustc error messages not only describe the error in the code, but for certain error patterns, suggest edits that may fix the problem. However, these edits are always local and don’t provide any high-level design feedback which may be helpful in…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2301.02308/"&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>The Usability of Advanced Type Systems: Rust as a Case Study — HN submission</title><link>https://news.ycombinator.com/item?id=34890787</link><guid isPermaLink="false">urn:hackerpapers:submission:2301.02308:34890787</guid><pubDate>Wed, 22 Feb 2023 02:27:16 GMT</pubDate><description>&lt;p&gt;The usability of advanced type systems: Rust as a case study&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;141 points; 162 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2301.02308/"&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>The Usability of Advanced Type Systems: Rust as a Case Study — HN submission</title><link>https://news.ycombinator.com/item?id=34879761</link><guid isPermaLink="false">urn:hackerpapers:submission:2301.02308:34879761</guid><pubDate>Tue, 21 Feb 2023 11:27:25 GMT</pubDate><description>&lt;p&gt;The Usability of Advanced Type Systems: Rust as a Case Study&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2301.02308/"&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>The Usability of Advanced Type Systems: Rust as a Case Study — HN submission</title><link>https://news.ycombinator.com/item?id=34310167</link><guid isPermaLink="false">urn:hackerpapers:submission:2301.02308:34310167</guid><pubDate>Mon, 09 Jan 2023 13:41:15 GMT</pubDate><description>&lt;p&gt;The Usability of Advanced Type Systems: Rust as a Case Study&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2301.02308/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
