<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Static-Analysis on The Smoking Duck Blog</title><link>https://blog.aabouzied.com/blog/static-analysis/</link><description>Recent content in Static-Analysis on The Smoking Duck Blog</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2021, Ahmed Abouzied.</copyright><lastBuildDate>Wed, 07 Oct 2026 04:34:55 +0200</lastBuildDate><atom:link href="https://blog.aabouzied.com/blog/static-analysis/index.xml" rel="self" type="application/rss+xml"/><item><title>goprove: A prover for Golang</title><link>https://blog.aabouzied.com/goprove-a-prover-for-golang/</link><pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate><guid>https://blog.aabouzied.com/goprove-a-prover-for-golang/</guid><description>&lt;p&gt;Now that AI is writing a lot of production code. We need to have as many checks and validators as possible to validate the code AI writes. That&amp;rsquo;s why I want to share &amp;ldquo;goprove&amp;rdquo;. A project I have been cooking for more than a month (by hand, AI helped a lot with testing for edge cases though).&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://goprove.dev/"&gt;goprove.dev&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;It&amp;rsquo;s a &amp;ldquo;prover&amp;rdquo; for Golang. A prover that mathematically proves that your Go code is safe against certain issues such as nil pointer panics and integer overflows. Go was not built for safe mission-critical software. You will not be building a medical ICU monitor in Go (well, I certainly hope not XD). That&amp;rsquo;s a C++ job with all the tools that prove C++ code and certify it against explicit safety certification standards. And Rust has been catching up to this game.&lt;/p&gt;</description></item></channel></rss>