<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Modular Information Flow through Ownership · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2111.13662/</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/2111.13662/feed.xml" rel="self" type="application/rss+xml" /><item><title>Modular Information Flow through Ownership — mentioned by Animats</title><link>https://news.ycombinator.com/item?id=45630462</link><guid isPermaLink="false">urn:hackerpapers:mention:2111.13662:45630462</guid><pubDate>Sat, 18 Oct 2025 21:24:43 GMT</pubDate><description>&lt;p&gt;Actual paper: [1] This could be useful. I&amp;#x27;ve been plugging away, on and off, on the concept of statically checked back-references for Rust. This is one of the biggest complaints that C/C++ people have about Rust - if A points to B, it&amp;#x27;s really hard to have a pointer from B to A. This leads to unsafe workarounds. You can do it safely with Rc, RefCell, Weak, borrow(), borrow_mut(), upgrade(), and downgrade(). It&amp;#x27;s verbose, adds run-time overhead, and there&amp;#x27;s the potential of panicking at run time on a double borrow. But the expressive power is there. This is work in progress, and I have some…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2111.13662/"&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>
