<p>Hi all<br/>
What is more expensive for memory datatype map or struct?</p>
<hr/>**评论：**<br/><br/>dgryski: <pre><p>A struct will always use less memory than a map storing the same keys/values. You also have more type safety with structs if your values aren't all the same type as a map would require them to be.</p></pre>RSoreil: <pre><p>I don't want to project too much of how C works on to Go but a struct is essentially nothing but a label for a set of datatypes stacked next to each other in memory. A quick look at the playground seems to comfirm this <a href="http://play.golang.org/p/Q9t-MSch6h">http://play.golang.org/p/Q9t-MSch6h</a></p>
<p>A map is a hashmap and will take a lot more memory to store the map.</p></pre>emadera52: <pre><p>There's no question that a map takes more memory. On the other hand, if your use case involves using a key to find a value (and the values are all of the same type), a map fills the bill without additional effort. That's not true if you have your keys and values stored as structs in an array. </p></pre>
