<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Generic Zero-Cost Reuse for Dependent Types · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1803.08150/</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/1803.08150/feed.xml" rel="self" type="application/rss+xml" /><item><title>Generic Zero-Cost Reuse for Dependent Types — mentioned by voxl</title><link>https://news.ycombinator.com/item?id=24147000</link><guid isPermaLink="false">urn:hackerpapers:mention:1803.08150:24147000</guid><pubDate>Thu, 13 Aug 2020 19:04:55 GMT</pubDate><description>&lt;p&gt;HoTT changes what equal means. In order for univalence to work you must be comfortable with arbitrary code running to perform the necessary substitutions. Isomorphism isn&amp;#x27;t for free, you can do some fancy cast-conversions (where cast is an identity function) that has been explored in generic zero-cost reuse [1] but this is not HoTT and uses essentially an UIP equality (which is inconsistent with HoTT). Your usage of the word &amp;quot;cast&amp;quot; in the second paragraph is a misnomer, because no systems programmer is going to want to perform an expensive transporation in HoTT! [1]…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1803.08150/"&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>
