<story><title>Program FPGAs with Go</title><url>https://reconfigure.io/</url></story><parent_chain></parent_chain><comment><author>jerf</author><text>This being the internet, let me preface this with this being honest questions, rather than attacks. I did try to read through the docs before asking but I don&amp;#x27;t see the answers directly.&lt;p&gt;Especially on the FPGA side, how does this interact with all the features of Go that seem ill-suited to an FPGA implementation? Can I write functions that generate and consume closures? Where is my garbage going on the FPGA side and how is it collected? Or is the FPGA code being written only in a subset of Go?&lt;p&gt;I understand the idea of wrapping the primitives offered by the FPGA hardware itself into channels, but I&amp;#x27;m unclear on how one can sensibly implement a Go runtime on top of that in the FPGA without making it too difficult to understand the cost model of your Go code.</text></comment>
<story><title>Program FPGAs with Go</title><url>https://reconfigure.io/</url></story><parent_chain></parent_chain><comment><author>rubenfiszel</author><text>Congrats!&lt;p&gt;We, a stanford lab, are pursuing similar goals but opensource and from a Scala DSL although our doc (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;spatial-lang.readthedocs.io&amp;#x2F;en&amp;#x2F;latest&amp;#x2F;tutorial&amp;#x2F;starting.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;spatial-lang.readthedocs.io&amp;#x2F;en&amp;#x2F;latest&amp;#x2F;tutorial&amp;#x2F;starti...&lt;/a&gt;) is not that up-to-date:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;stanford-ppl&amp;#x2F;spatial-lang&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;stanford-ppl&amp;#x2F;spatial-lang&lt;/a&gt;</text></comment>