if int and int32 the same, why golang keeps these two?

<p>tbh, this raises confusing if you were programming in java or cpp</p> <hr/>**评论：**<br/><br/>iroflmaowtf: <pre><p><a href="https://golang.org/pkg/builtin/#int" rel="nofollow">https://golang.org/pkg/builtin/#int</a></p> <blockquote> <p>int is a signed integer type that is <strong><em>at least 32 bits in size</em></strong>. It is a distinct type, however, and <strong><em>not an alias for, say, int32.</em></strong></p> </blockquote></pre>: <pre><p>[deleted]</p></pre>TheMerovius: <pre><blockquote> <p>int is 64 bits on 64-bit platforms, and 32 bits on 32-bit platforms.</p> </blockquote> <p>nit: int is either int32 or int64; an implementation can choose whatever it wants, no matter what platform it runs on (for example, GopherJS on my laptop runs on a 64 bit platform, but uses int32 for ints, as they have to fit in a float64).</p></pre>nsd433: <pre><p>As others have said, int and int32 are not the same, and that&#39;s why you have both. Most of the time you want a reasonable int. Other times you want an int which truncates at 32 bits.</p> <p>You mention C++. C and C++ have the same destinction. In C/C++ &#39;int&#39; is a reasonable integer size on the target CPU, and int32_t is a signed integer with exactly 32 bits.</p></pre>faiface: <pre><p>Surprised no one mentioned that int usually has 64 bits on 64-bit systems and 32 bits on 32-bit systems. The distinction from both int32 and int64 is clear.</p></pre>irene634: <pre><p>If that is correct, it is the same to use int and int64 on 64-bit systems? </p></pre>faiface: <pre><p>No. On 64-bit systems, both types allow same sets of values, but are different in the Go type system and values of one need to be explicitly converted to the other.</p></pre>