<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reactive Imperative Programming with Dataflow Constraints · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1104.2293/</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/1104.2293/feed.xml" rel="self" type="application/rss+xml" /><item><title>Reactive Imperative Programming with Dataflow Constraints — mentioned by mpweiher</title><link>https://news.ycombinator.com/item?id=29681129</link><guid isPermaLink="false">urn:hackerpapers:mention:1104.2293:29681129</guid><pubDate>Sat, 25 Dec 2021 06:59:23 GMT</pubDate><description>&lt;p&gt;&amp;gt;&amp;gt; It means you work with constraints, for example dataflow constraints. &amp;gt; I&amp;#x27;m not sure anyone else would call that anything but an interface I am sure that nobody calls that an &amp;quot;interface&amp;quot;. First, a dataflow constraint is nothing like an interface (for one it is an implementation). It&amp;#x27;s also a standard term of art. https://www.cs.cmu.edu/~amulet/papers/toplas-constraint-expe... https://arxiv.org/abs/1104.2293 http://web.eecs.utk.edu/~bvanderz/quickplan.html http://www.hosobe.org/wp-content/uploads/iccae2020.pdf ... &amp;gt; This is obvious and not adhering to that is unmaintainable, due to…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1104.2293/"&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>
