<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Struct-Mapping on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/struct-mapping/</link>
    <description>Recent content in Struct-Mapping on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/struct-mapping/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>mapstructure vs mergo vs copier in 2026: Go Struct Mapping and Copying Done Right</title>
      <link>https://www.pistack.xyz/posts/2026-08-13-go-struct-mapping-libraries-mapstructure-mergo-copier/</link>
      <pubDate>Thu, 13 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-13-go-struct-mapping-libraries-mapstructure-mergo-copier/</guid>
      <description>&lt;p&gt;Every Go developer has written the same two loops a hundred times: the one that decodes a &lt;code&gt;map[string]interface{}&lt;/code&gt; into a typed struct field by field, and the one that copies fields from one struct to another. Both are boring, repetitive, and a reliable source of subtle bugs — and both have battle-tested open-source solutions that most teams still reimplement by hand. &lt;strong&gt;mapstructure&lt;/strong&gt;, &lt;strong&gt;mergo&lt;/strong&gt;, and &lt;strong&gt;copier&lt;/strong&gt; are the three libraries that eliminate this boilerplate, and they solve &lt;em&gt;different&lt;/em&gt; problems. Here is when to reach for each.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
