<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Programming on Simple Enough Blog</title><link>https://blog-dev.simpleenough.net/tags/programming/</link><description>Recent content in Programming on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 15 Nov 2025 10:00:00 +0200</lastBuildDate><atom:link href="https://blog-dev.simpleenough.net/tags/programming/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Handle Optional Parameters in Go</title><link>https://blog-dev.simpleenough.net/blog/optiongo/</link><pubDate>Sat, 15 Nov 2025 10:00:00 +0200</pubDate><guid>https://blog-dev.simpleenough.net/blog/optiongo/</guid><description>&lt;h1 id="i-how-to-handle-optional-parameters-in-go" class="heading">I. How to Handle Optional Parameters in Go&lt;a href="#i-how-to-handle-optional-parameters-in-go" aria-labelledby="i-how-to-handle-optional-parameters-in-go">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>
&lt;p>In most modern languages, you can define default values for function parameters or overload functions to cover various use cases.&lt;br>
Go, however, offers &lt;strong>no optional parameters&lt;/strong>, &lt;strong>no overloading&lt;/strong>, and &lt;strong>no default values&lt;/strong> in function signatures.&lt;br>
Yet the needs remain the same: creating readable, stable APIs that can evolve without breaking users.&lt;/p></description></item></channel></rss>