Go Concepts - The Type System: Difference between revisions
Line 52: | Line 52: | ||
=Conversion Between Types= | =Conversion Between Types= | ||
In order to convert between types, the type name is used like a function: | |||
<pre> | |||
var f float64 = 5.0 | |||
var i int = 5 | |||
var result float64 | |||
result = f / float64(i) | |||
</pre> | |||
=Primitive vs. Non-Primitive Nature= | =Primitive vs. Non-Primitive Nature= |
Revision as of 22:41, 27 March 2016
Internal
Overview
Go is statically typed. Go designers tried to alleviate some of the "heaviness" associated with statically typed languages and made it "feel" like a dynamic language. For example Go uses local type inference, which eliminates the need to specify the type unnecessarily in program, the compiler figures it out.
Go is strongly typed meaning that yes cannot be unsafely coerced into other types they're not, or at least without programmer giving explicit permission. In JavaScript, for example, implicit conversion is done based on complicated rules that are not always easy to remember.
For more details on typing, see static typing vs. dynamic typing and strong typing vs. loose typing.
Type Definition
Built-in Types
User-Defined Types
Interfaces
Interfaces are not types.
Can only structs be interfaces, or there are other things that can be interfaces?
Zero Value
Zero value for a specific type: 0 for ints, 0.0 for floats, "" for string, false for Booleans and nil for pointers. For reference types, their underlying data structures are initialized to their zero values.
Reference Types
Value and Reference Types
Conversion Between Types
In order to convert between types, the type name is used like a function:
var f float64 = 5.0 var i int = 5 var result float64 result = f / float64(i)
Primitive vs. Non-Primitive Nature
Duck Typing
For more details on duck typing go here.