<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Language on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/language/</link>
    <description>Recent content in Language on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2020 11:13:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/language/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Generics Are Coming to Go: What the Proposal Actually Solves</title>
      <link>https://blog.turboawesome.win/2020/10/generics-are-coming-to-go-what-the-proposal-actually-solves/</link>
      <pubDate>Mon, 05 Oct 2020 11:13:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2020/10/generics-are-coming-to-go-what-the-proposal-actually-solves/</guid>
      <description>The generics proposal for Go landed in 2020 and the feature shipped in Go 1.18. Here&amp;#39;s what the design was targeting, what it actually enables, and why the &amp;#39;just use interface{}&amp;#39; crowd was always missing the point.</description>
    </item>
  </channel>
</rss>
