<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>News on Clash</title>
    <link>https://clash-lang.org/categories/news/</link>
    <description>Recent content in News on Clash</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://clash-lang.org/categories/news/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Shockwaves: Typed waveforms for Clash</title>
      <link>https://clash-lang.org/blog/2026-04-21-shockwaves/</link>
      <pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://clash-lang.org/blog/2026-04-21-shockwaves/</guid>
      <description>For years, debugging Clash designs in a waveform viewer has been a massive pain. After all, the waveform viewers we have were not designed with Clash in mind, and glady present us with unintelligible binary values. But those times are now over! I&amp;rsquo;ve spent the last months working on Shockwaves, a system that lets you show typed waveforms in (Surfer)[https://surfer-project.org/], and after many, &lt;em&gt;many&lt;/em&gt; changes, tests, bug fixes and rewrites, we have finally reached the point of an official release!</description>
    </item>
    <item>
      <title>Introducing checked-literals: compile-time bounds checking for numeric literals</title>
      <link>https://clash-lang.org/blog/2026-04-07-checked-literals/</link>
      <pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://clash-lang.org/blog/2026-04-07-checked-literals/</guid>
      <description>GHC&amp;rsquo;s builtin overflow warnings are easy to bypass and don&amp;rsquo;t work for custom numeric types. We wrote a GHC source plugin, &lt;code&gt;checked-literals&lt;/code&gt;, that rewrites numeric literals so that out-of-range values are rejected at compile time. It works in monomorphic and polymorphic contexts, supports integer and rational literals, and produces actionable error messages &amp;ndash; including suggested type-level constraints.</description>
    </item>
    <item>
      <title>Clash 1.4 released</title>
      <link>https://clash-lang.org/blog/2021-03-12-clash14/</link>
      <pubDate>Fri, 12 Mar 2021 00:00:00 +0000</pubDate>
      <guid>https://clash-lang.org/blog/2021-03-12-clash14/</guid>
      <description>We&amp;rsquo;ve just released Clash 1.4 to the world. We&amp;rsquo;ve summarized the most important changes in this blogpost.</description>
    </item>
    <item>
      <title>Clash 1.2.2 and future plans</title>
      <link>https://clash-lang.org/blog/2020-06-14-clash122/</link>
      <pubDate>Sun, 14 Jun 2020 00:00:00 +0000</pubDate>
      <guid>https://clash-lang.org/blog/2020-06-14-clash122/</guid>
      <description>Last Friday we released Clash 1.2.2 on GitHub. In big part thanks to our lovely community, we&amp;rsquo;ve found and fixed many bugs. Thanks to some patches, Clash even runs anywhere from 2-20% faster for some common design patterns! With this blogpost I&amp;rsquo;d like to highlight some of the progress we&amp;rsquo;ve made since the 1.2 release, and elaborate on our future plans.</description>
    </item>
    <item>
      <title>Clash 1.2 released</title>
      <link>https://clash-lang.org/blog/2020-03-05-clash12/</link>
      <pubDate>Thu, 05 Mar 2020 00:00:00 +0000</pubDate>
      <guid>https://clash-lang.org/blog/2020-03-05-clash12/</guid>
      <description>&lt;p&gt;As promised when releasing 1.0, we&amp;rsquo;ve tried our best to keep the API stable. We&#xA;think most designs will continue to compile with this new version, although special&#xA;care needs to be taken when using:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;..inline blackboxes. Instead of taking a single HDL, inline primitives now&#xA;take multiple. For example, &lt;code&gt;InlinePrimitive VHDL &amp;quot;..&amp;quot;&lt;/code&gt; must now be written&#xA;as &lt;code&gt;InlinePrimitive [VHDL] &amp;quot;..&amp;quot;&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;..the &lt;code&gt;Enum&lt;/code&gt; instance for &lt;code&gt;BitVector&lt;/code&gt;, &lt;code&gt;Index&lt;/code&gt;, &lt;code&gt;Signed&lt;/code&gt;, or &lt;code&gt;Unsigned&lt;/code&gt;, as&#xA;they now respect their &lt;code&gt;maxBound&lt;/code&gt;. See &lt;a href=&#34;https://github.com/clash-lang/clash-compiler/issues/1089&#34;&gt;#1089&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Clash 1.0 released!</title>
      <link>https://clash-lang.org/blog/2019-09-04-clash10/</link>
      <pubDate>Wed, 04 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://clash-lang.org/blog/2019-09-04-clash10/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s here! &lt;strong&gt;Clash 1.0&lt;/strong&gt; is finally released! And it has a binary release for the very first time!&#xA;Check out the &lt;a href=&#34;https://clash-lang.org/install/&#34;&gt;install instructions&lt;/a&gt; instructions on how to get it!&lt;/p&gt;&#xA;&lt;h1 id=&#34;10-years-old&#34;&gt;10 years old&lt;/h1&gt;&#xA;&lt;p&gt;First a short retrospective: the very first demonstration of the Clash compiler was given on the 3rd of September 2009 at the Haskell&#39;09 Symposium in Edinburgh: &#xA;      &lt;div&#xA;          style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;        &lt;iframe&#xA;          src=&#34;https://player.vimeo.com/video/6680861?dnt=0&#34;&#xA;            style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; allow=&#34;fullscreen&#34;&gt;&#xA;        &lt;/iframe&gt;&#xA;      &lt;/div&gt;&#xA;&#xA;We were planning the 1.0 release of Clash for some time now, but decided that such a momentous occasion should coincide with the 10 year anniversary of Clash (+1 day due to release engineering mishaps).&#xA;We really want to thank all of our contributors for their continued support of Clash.&#xA;The &lt;a href=&#34;https://github.com/clash-lang/clash-compiler/graphs/contributors&#34;&gt;code contributors&lt;/a&gt; that invest their time to create new features and fix bugs, and the &lt;a href=&#34;https://github.com/clash-lang/clash-compiler/blob/master/LICENSE&#34;&gt;financial contributors&lt;/a&gt; that enable the core Clash developers to work on Clash as their day job.&#xA;Much praise for our users as well, who&amp;rsquo;ve struggled through our API changes over the years (which should happen much, much, less from now on), who helped us pinpoint many bugs and thus making Clash a more stable piece of software.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New website!</title>
      <link>https://clash-lang.org/blog/2018-11-20-welcome/</link>
      <pubDate>Tue, 20 Nov 2018 00:00:00 +0000</pubDate>
      <guid>https://clash-lang.org/blog/2018-11-20-welcome/</guid>
      <description>&lt;p&gt;Welcome to the new &lt;strong&gt;Clash&lt;/strong&gt; website!&#xA;While the &lt;a href=&#34;http://clash-lang.github.io&#34;&gt;old website&lt;/a&gt; served us well, we wanted to have support for a &lt;a href=&#34;https://clash-lang.org/blog/&#34;&gt;blog&lt;/a&gt;: go check out our first two posts on &lt;a href=&#34;https://clash-lang.org/blog/2018-07-09-matrix-multiplication/&#34;&gt;matrix multiplication&lt;/a&gt; and &lt;a href=&#34;https://clash-lang.org/blog/2018-07-25-systolic-arrays/&#34;&gt;systolic arrays&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;We wanted a static website for all the usual reasons (speed, security, etc), and decided to use &lt;a href=&#34;https://gohugo.io&#34;&gt;hugo&lt;/a&gt; because:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;It&amp;rsquo;s &lt;a href=&#34;https://www.staticgen.com/&#34;&gt;popular&lt;/a&gt;, and consequently has many resources on how to customize and setup a site.&lt;/li&gt;&#xA;&lt;li&gt;Is simple to install because it&amp;rsquo;s a single statically compiled binary.&lt;/li&gt;&#xA;&lt;li&gt;It has a lot of features, including i18n support which we eventually want to use to have translated versions of our blog posts.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;We&amp;rsquo;re using &lt;a href=&#34;https://netlify.com&#34;&gt;netlify&lt;/a&gt; to host the website because:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
