<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Go on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/go/</link>
    <description>Recent content in Go on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Sep 2020 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/go/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Finding Goroutine Bugs with TLA&#43;</title>
      <link>https://www.hillelwayne.com/post/tla-golang/</link>
      <pubDate>Fri, 25 Sep 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/tla-golang/</guid>
      <description>My job these days is teaching TLA+ and formal methods: specifying designs to find bugs in them. But just knowing the syntax isn&amp;rsquo;t enough to write specs, and it helps to have examples to draw from. I recently read Chris Siebenmann&amp;rsquo;s Even in Go, concurrency is still not easy and thought it would make a good case study for writing a spec. In it, he gives an example of Go code which deadlocks:</description>
    </item>
    
  </channel>
</rss>