Go Concepts - The Type System: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Internal=
=TODO=


* [[Go Concepts#Subjects|Concepts]]
<font color=darkkhaki>Deplete into [[Go_Language#The_Type_System]] and delete.


=Overview=
=Overview=


Go is ''statically typed''. Go designers tried to alleviate some of the "[[Programming#Static_Typing_vs_Dynamic_Typing|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 ''statically typed''. Go designers tried to alleviate some of the "[[Programming_Languages_Concepts#Static_Typing_vs_Dynamic_Typing|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.
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 [[Programming#Static_Typing_vs_Dynamic_Typing|static typing vs. dynamic typing]] and [[Programming#Strong_Typing_vs_Loose_Typing|strong typing vs. loose typing]].
For more details on typing, see [[Programming_Languages_Concepts#Static_Typing_vs_Dynamic_Typing|static typing vs. dynamic typing]] and [[Programming_Languages_Concepts#Strong_Typing_vs_Loose_Typing|strong typing vs. loose typing]].


Go provides a ''hierarchy-free'' type system - there are no classes and no class inheritance. It is still an object-oriented language. Go type system encourages ''composition'', where types are ''composed'' of smaller types.
Go provides a ''hierarchy-free'' type system - there are no classes and no class inheritance. It is still an object-oriented language. Go type system encourages ''composition'', where types are ''composed'' of smaller types.
Line 16: Line 16:


<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[Programming#Type|Type Definition]]
:[[Programming_Languages_Concepts#Type|Type Definition]]
</blockquote>
</blockquote>


Line 31: Line 31:
===<tt>[[Go Booleans|bool]]</tt>===
===<tt>[[Go Booleans|bool]]</tt>===
===[[Go Integers|Integers]]===
===[[Go Integers|Integers]]===
===[[Go Floating-Point Numbers|Floating-Point Numbers]]===
 
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[Go Integers|Integers]]
</blockquote>
 
===[[Go Floating Point|Floating-Point Numbers]]===
===<tt>[[Go Strings|string]]</tt>===
===<tt>[[Go Strings|string]]</tt>===
===[[Go Arrays|Arrays]]===
===[[Go Arrays|Arrays]]===
===[[Go Slices|Slices]]===
===[[Go Slices|Slices]]===
===[[Go Maps|Maps]]===
===[[Go Maps|Maps]]===
===<tt>[[Go_Concepts_-_Error_Handling#The_error_Type|error]]</tt>===
===<tt>[[Go Language Error Handling#The_error_Type|error]]</tt>===


=Function Types=
=Function Types=
Line 78: Line 83:
</pre>
</pre>


The difference between a base type and its associated pointer type is also relevant when we are discussing whether the type and its pointer type implement an interface. For a discussion on this subject, see [[Go_Interfaces#When_does_a_Type.2FPointer_Type_Implement_an_Interface.3F|When does a Type/Pointer Type Implement an Interface?]].
The difference between a base type and its associated pointer type is also relevant when we are discussing whether the type and its pointer type implement an interface. For a discussion on this subject, see:
 
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[Go_Interfaces#When_does_a_Type.2FPointer_Type_Implement_an_Interface.3F|When does a Type/Pointer Type Implement an Interface?]]
</blockquote>


A ''pointer type'' is declared using the [[Go_Concepts_-_Operators#.2A|dereference operator]] <tt>[[Go_Concepts_-_Operators#.2A|*]]</tt> placed in front of the target type - the type of the stored value:
A ''pointer type'' is declared using the [[Go_Concepts_-_Operators#.2A|dereference operator]] <tt>[[Go_Concepts_-_Operators#.2A|*]]</tt> placed in front of the target type - the type of the stored value:
Line 93: Line 102:


The user-defined types are introduced by the <tt>type</tt> keyword. There are three kinds of user-defined types: 1) <tt>struct</tt>s 2) type aliasing and 3) interfaces. Behavior can be added to <tt>struct</tt>s and aliased types by the way of [[Go_Concepts_-_Functions#Methods|methods]].
The user-defined types are introduced by the <tt>type</tt> keyword. There are three kinds of user-defined types: 1) <tt>struct</tt>s 2) type aliasing and 3) interfaces. Behavior can be added to <tt>struct</tt>s and aliased types by the way of [[Go_Concepts_-_Functions#Methods|methods]].
The documentation sometimes refers to user-defined types as ''named types''.


===[[Go Structs|Structs]]===
===[[Go Structs|Structs]]===
Line 174: Line 185:


These fields are are initialized by default to their [[#Zero_Value|zero values]]. However, variable declared as a reference type set to their zero values will return a value of <tt>nil</tt>.
These fields are are initialized by default to their [[#Zero_Value|zero values]]. However, variable declared as a reference type set to their zero values will return a value of <tt>nil</tt>.
=Primitive vs. Non-Primitive Nature=
A type is said to have a ''primitive nature'' if adding or removing something from its value creates a new value. When passing values of these type to functions, a copy of the value should be passed. Integers, floats, booleans and strings are primitive data values.
For non-primitive types, the value itself is changed, and no copy is made. Values of non-primitve types are unsafe to copy. When a factory function returns a pointer, it's a good indication that the nature of the value being returned is non-primitive.
<tt>[[Go Structs|struct]]s</tt> can represent data values that could have either a primitive or non-primitive value. "Primitive" structs imply creating a new instance every time an existing value is mutated. In this case, values themselves, rather than pointers, are used to share values of those structs. An example is the <tt>Time</tt> structure in <tt>time.go</tt>. However, in most cases, structs exhibit a non-primitive structure: adding or removing something from the value mutates the value, does not create a new value.
The type of receiver (value vs. pointer) should be decided based on the nature of the receiver type. More details: [[Go_Concepts_-_Functions#Receiver_Best_Practice|receiver best practices]].
More details: Go in Action Section 5.3 "The Nature of Types".

Latest revision as of 17:31, 20 March 2024

TODO

Deplete into Go_Language#The_Type_System and delete.

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.

Go provides a hierarchy-free type system - there are no classes and no class inheritance. It is still an object-oriented language. Go type system encourages composition, where types are composed of smaller types.

Type Definition

Type Definition

Zero Value

Zero value for a specific type: 0 for ints, 0.0 for floats, "" for strings, false for Booleans and nil for pointers (0x0).

For reference types, their underlying data structures are initialized to their zero values, but variable declared as a reference type set to their zero values will return a value of nil. For example, the zero value for maps, slices and channels is nil.

Built-in Types

The built-in types are the set of types that are provided by the language. The definition of the following types can be found in $GO_HOME/src/builtin/builtin.go:

bool

Integers

Integers

Floating-Point Numbers

string

Arrays

Slices

Maps

error

Function Types

A function is member of a function type. The function type is defined by its signature:

func(input_param_type1, input_param_type2, ...) (return_type1, return_type2, ...)

Example of a function that requires an int and returns an int:

func(int) int
// a variable of type func(int) int is declared
var f func(int) int;

// the variable is initialized with an actual function
f = func(i int) int {
    return i + 1
}

Also see:

Function Literals

Pointer Types

A pointer type denotes the set of all pointers to variables of a given type, called the base type of the pointer.

Note that the base type and the associated pointer type are obviously two different types. Values of one cannot be assigned to another, and vice-versa. This is what happens when such an assignment is attempted:

./main.go:24: cannot use v2 (type *B) as type B in assignment

The difference between a base type and its associated pointer type is also relevant when we are discussing whether the type and its pointer type implement an interface. For a discussion on this subject, see:

When does a Type/Pointer Type Implement an Interface?

A pointer type is declared using the dereference operator * placed in front of the target type - the type of the stored value:

*int

We cannot do pointer arithmetic. Assuming ptr is a *int, we cannot do ptr + 1 (compilation error message: invalid operation: ptr + 1 (mismatched types *int and int)) and we can't do ptr + ptr2 (compilation error message: invalid operation: ptr + ptr2 (operator + not defined on pointer)).

For more details, see pointers.

User-Defined Types

The user-defined types are introduced by the type keyword. There are three kinds of user-defined types: 1) structs 2) type aliasing and 3) interfaces. Behavior can be added to structs and aliased types by the way of methods.

The documentation sometimes refers to user-defined types as named types.

Structs

struct

Type Aliasing

Type Aliasing

Interfaces

Interfaces

Declaring Multiple Types

type (

     A struct {
         ...
     }
     
     B struct {
         ...
     }

    ...
)

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
...
result = f / float64(i)

This is equivalent with Java cast.

Note that the same syntax can be used to convert to and from user-defined types:

import "time"

...

var sleepSeconds int
sleepSeconds = 1

//
// time.Sleep expects a time.Duration do we convert time.Second to int, multiply and convert back to time.Duration
//
var duration time.Duration
duration = time.Duration(sleepSeconds * int(time.Second))
time.Sleep(duration)

Also see:

Conversion between bytes and strings

Reference Types

The reference types in Go are slices, maps, channels, interfaces and functions.

When a variable of such a type is declared, the value that is created is called a header value. The header contains pointers to underlying data structures and a set of unique fields that are used to manage those data structures. Reference type values must not be shared, because the header values are designed to be copied: the header value contains a pointer, therefore if a copy of the header value is passed, the underlying data structure is intrinsically shared.

These fields are are initialized by default to their zero values. However, variable declared as a reference type set to their zero values will return a value of nil.