Go Concepts - The Type System: Difference between revisions
No edit summary |
|||
Line 33: | Line 33: | ||
:[[Go Structs|structs]] | :[[Go Structs|structs]] | ||
</blockquote> | </blockquote> | ||
==Interfaces== | ==Interfaces== | ||
Line 40: | Line 39: | ||
<font color=red>Can only structs be interfaces, or there are other things that can be interfaces?</font> | <font color=red>Can only structs be interfaces, or there are other things that can be interfaces?</font> | ||
=Value and Reference Types= | =Value and Reference Types= |
Revision as of 17:24, 22 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?
Value and Reference Types
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
Conversion Between Types
Primitive vs. Non-Primitive Nature
Duck Typing
For more details on duck typing go here.