<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Strings on A Blog for the Uninitialized</title><link>https://www.nilpointer.blog/tags/strings/</link><description>Recent content in Strings on A Blog for the Uninitialized</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank" rel="noopener"&gt;Licensed under Apache 2.0&lt;/a&gt;</copyright><lastBuildDate>Tue, 10 Mar 2026 15:00:17 -0700</lastBuildDate><atom:link href="https://www.nilpointer.blog/tags/strings/index.xml" rel="self" type="application/rss+xml"/><item><title>Building strings in Golang</title><link>https://www.nilpointer.blog/posts/2026/03/building-strings-in-golang/</link><pubDate>Tue, 10 Mar 2026 15:00:17 -0700</pubDate><guid>https://www.nilpointer.blog/posts/2026/03/building-strings-in-golang/</guid><description>&lt;p&gt;&lt;strong&gt;How do I build a string in Golang?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Building a string seems trivial, and it generally is, but it&amp;rsquo;s a great way to dive into further to understand some of the basics around what makes Golang so interesting.&lt;/p&gt;
&lt;p&gt;First of all, let&amp;rsquo;s note that a &lt;em&gt;string&lt;/em&gt; in Golang is &lt;em&gt;immutable&lt;/em&gt;. That means whenever you want to append to a string, the existing string &lt;em&gt;plus what you&amp;rsquo;re appending&lt;/em&gt; needs to be copied to a new string in memory. This means that when optimizing code, we need to be mindful when we write code that performs these actions many times.&lt;/p&gt;</description></item></channel></rss>