<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="type MyDatabaseTable struct {
    SomeDescription            string `db:&quot;some_description&quot; json:&quot;some_description&quot;`
}"><pre class="notranslate"><code class="notranslate">type MyDatabaseTable struct {
    SomeDescription            string `db:"some_description" json:"some_description"`
}
</code></pre></div>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="type MyDatabaseTable struct {
    SomeDescription            string `db, json:&quot;some_description&quot;`
}"><pre class="notranslate"><code class="notranslate">type MyDatabaseTable struct {
    SomeDescription            string `db, json:"some_description"`
}
</code></pre></div>
<p dir="auto">To make it consistent with the <code class="notranslate">:=</code> and <code class="notranslate">=</code> operator when assigning variables. I think it's a common case to have for example a db and json tag that have the same value.</p>
<p dir="auto"><a href="http://play.golang.org/p/Tva1Cpulrh" rel="nofollow">http://play.golang.org/p/Tva1Cpulrh</a></p>
<p dir="auto">The builder has little to say:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="signal: segmentation fault (core dumped)
FAIL    image/draw  0.367s"><pre class="notranslate"><code class="notranslate">signal: segmentation fault (core dumped)
FAIL    image/draw  0.367s
</code></pre></div>
<p dir="auto">Appears to be independent of other failures, will investigate tomorrow.</p>