<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dialyzer on Scholion</title><link>https://scholion.thluiz.com/tags/dialyzer/</link><description>Recent content in Dialyzer on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Wed, 18 Nov 2026 13:08:13 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/dialyzer/index.xml" rel="self" type="application/rss+xml"/><item><title>Decoding Dialyzer - Part 1</title><link>https://scholion.thluiz.com/notes/decoding-dialyzer-common-warnings-part-1/</link><pubDate>Tue, 17 Nov 2026 15:00:51 +0000</pubDate><guid>https://scholion.thluiz.com/notes/decoding-dialyzer-common-warnings-part-1/</guid><description>Explains two common Dialyzer warnings (&lt;code&gt;no_return&lt;/code&gt; and &lt;code&gt;call&lt;/code&gt;), how they arise from a simple Elixir bug, what success typings vs contracts mean, and how to fix the issue.</description></item><item><title>Designing For Elixir Compiler Hints</title><link>https://scholion.thluiz.com/notes/designing-for-elixir-compiler-hints/</link><pubDate>Mon, 16 Nov 2026 20:08:27 +0000</pubDate><guid>https://scholion.thluiz.com/notes/designing-for-elixir-compiler-hints/</guid><description>Author examines Elixir 1.11 struct-field compile-time checks, arguing they give limited benefit, complicate polymorphic design, and shouldn’t drive application architecture.</description></item><item><title>Enforcing code quality in Elixir</title><link>https://scholion.thluiz.com/notes/enforcing-code-quality-in-elixir/</link><pubDate>Thu, 04 Jul 2019 11:04:40 +0000</pubDate><guid>https://scholion.thluiz.com/notes/enforcing-code-quality-in-elixir/</guid><description>The article sets up a Mix alias for Elixir projects that runs format, Credo, Sobelow, Dialyzer, and tests locally and in CI, with warnings treated as errors.</description></item></channel></rss>