Composite Types
Composite types allow composing simpler types into more complex types. For example, they allow the composition of multiple values into one. Composite types have a name and consist of zero or more named fields and zero or more functions that operate on the data. Each field may have a different type.
Composite types can only be declared within a contract and nowhere else.
There are two kinds of composite types:
- Structures are copied — they are value types. Structures are useful when copies with an independent state are desired.
- Resources are moved — they are linear types and must be used exactly once. Resources are useful when it is desired to model ownership (a value exists exactly in one location and it should not be lost).
Each kind differs in its usage and behavior, depending on when the value is:
- used as the initial value for a constant or variable
- assigned to a variable
- passed as an argument to a function, and
- returned from a function.
Certain constructs in a blockchain represent assets of real, tangible value, as much as a house, car, or bank account. We must consider the possiblity of literal loss and theft, perhaps even on the scale of millions of dollars.
Structures are not an ideal way to represent this ownership because they can be copied. This would mean that there could be a risk of having multiple copies of certain assets floating around, which breaks the scarcity requirements needed for these assets to have real value and calls into question who actually owns the property.
A structure is much more useful for representing information that can be grouped together in a logical way, but doesn't have value or a need to be able to be owned or transferred.
A structure could for example be used to contain the information associated with a division of a company, but a resource would be used to represent the assets that have been allocated to that organization for spending.
Nesting of resources is only allowed within other resource types, or in data structures like arrays and dictionaries, but not in structures, as that would allow resources to be copied.
Composite type declaration and creation
Structures are declared using the struct
keyword, and resources are declared using the resource
keyword. The keyword is followed by the name:
_10access(all)_10struct SomeStruct {_10 // ..._10}_10_10access(all)_10resource SomeResource {_10 // ..._10}
- Structures and resources are types.
- Structures are created (instantiated) by calling the type like a function.
_10// instantiate a new struct object and assign it to a constant_10let a = SomeStruct()
The constructor function may require parameters if the initializer of the composite type requires them.
Composite types can only be declared within contracts and not locally in functions.
- A resource must be created (instantiated) by using the
create
keyword and calling the type like a function. - Resources can only be created in functions and types that are declared in the same contract in which the resource is declared.
_10// instantiate a new resource object and assign it to a constant_10let b <- create SomeResource()
Composite type fields
Fields are declared like variables and constants. However, the initial values for fields are set in the initializer, not in the field declaration. All fields must be initialized in the initializer, exactly once.
Having to provide initial values in the initializer might seem restrictive, but this ensures that all fields are always initialized in one location, the initializer, and the initialization order is clear.
The initialization of all fields is checked statically and it is invalid to not initialize all fields in the initializer. Also, it is statically checked that a field is definitely initialized before it is used.
The initializer's main purpose is to initialize fields, though it may also contain other code. Just like a function, it may declare parameters and may contain arbitrary code. However, it has no return type (i.e., it is always Void
).
- The initializer is declared using the
init
keyword. - The initializer always follows any fields.
There are two kinds of fields:
-
Constant fields — are also stored in the composite value, but after they have been initialized with a value, they cannot have new values assigned to them afterwards. A constant field must be initialized exactly once.
Constant fields are declared using the
let
keyword. -
Variable fields — are stored in the composite value and can have new values assigned to them.
Variable fields are declared using the
var
keyword.Field Kind Assignable Keyword Variable field Yes var
Constant field No let
In initializers, the special constant self
refers to the composite value that is to be initialized.
If a composite type is to be stored, all of its field types must be storable. Non-storable types are:
- Functions
- Accounts —
Account
- Transactions
- References — References are ephemeral. Consider storing a capability and borrowing it when needed instead.
Fields can be read (if they are constant or variable) and set (if they are variable), using the access syntax: the composite value is followed by a dot (.
) and the name of the field.
_23// Declare a structure named `Token`, which has a constant field_23// named `id` and a variable field named `balance`._23//_23// Both fields are initialized through the initializer._23//_23// The public access modifier `access(all)` is used in this example to allow_23// the fields to be read in outer scopes. Fields can also be declared_23// private so they cannot be accessed in outer scopes._23//_23access(all)_23struct Token {_23_23 access(all)_23 let id: Int_23_23 access(all)_23 var balance: Int_23_23 init(id: Int, balance: Int) {_23 self.id = id_23 self.balance = balance_23 }_23}
It is invalid to provide the initial value for a field in the field declaration.
_10access(all)_10struct StructureWithConstantField {_10 // Invalid: It is invalid to provide an initial value in the field declaration._10 // The field must be initialized by setting the initial value in the initializer._10 //_10 access(all)_10 let id: Int = 1_10}
The field access syntax must be used to access fields — fields are not available as variables.
_13access(all)_13struct Token {_13_13 access(all)_13 let id: Int_13_13 init(initialID: Int) {_13 // Invalid: There is no variable with the name `id` available._13 // The field `id` must be initialized by setting `self.id`._13 //_13 id = initialID_13 }_13}
The initializer is not automatically derived from the fields. It must be explicitly declared.
_10access(all)_10struct Token {_10_10 access(all)_10 let id: Int_10_10 // Invalid: Missing initializer initializing field `id`._10}
A composite value can be created by calling the constructor and providing the field values as arguments.
The value's fields can be accessed on the object after it is created:
_11let token = Token(id: 42, balance: 1_000_00)_11_11token.id // is `42`_11token.balance // is `1_000_000`_11_11token.balance = 1_11// `token.balance` is `1`_11_11// Invalid: assignment to constant field_11//_11token.id = 23
Initializers do not support overloading.
Initializers can also be declared with the view
keyword to indicate that they do not perform any mutating operations and to allow them to be called from within other view
functions. In an initializer, writes to self
are considered view
(unlike within other composite functions), as the value being constructed here is by definition local to the context calling the initializer:
_14access(all)_14struct Token {_14_14 access(all)_14 let id: Int_14_14 access(all)_14 var balance: Int_14_14 view init(id: Int, balance: Int) {_14 self.id = id_14 self.balance = balance_14 }_14}
Composite type functions
Composite types may contain functions. Just like in the initializer, the special constant self
refers to the composite value that the function is called on:
_31// Declare a structure named "Rectangle", which represents a rectangle_31// and has variable fields for the width and height._31//_31access(all)_31struct Rectangle {_31_31 access(all)_31 var width: Int_31_31 access(all)_31 var height: Int_31_31 init(width: Int, height: Int) {_31 self.width = width_31 self.height = height_31 }_31_31 // Declare a function named "scale", which scales_31 // the rectangle by the given factor._31 //_31 access(all)_31 fun scale(factor: Int) {_31 self.width = self.width * factor_31 self.height = self.height * factor_31 }_31}_31_31let rectangle = Rectangle(width: 2, height: 3)_31rectangle.scale(factor: 4)_31// `rectangle.width` is `8`_31// `rectangle.height` is `12`
Functions do not support overloading.
Composite type subtyping
Two composite types are compatible if and only if they refer to the same declaration by name (i.e., nominal typing applies instead of structural typing).
Even if two composite types declare the same fields and functions, the types are only compatible if their names match:
_28// Declare a structure named `A` which has a function `test`_28// which has type `fun(): Void`._28//_28struct A {_28 fun test() {}_28}_28_28// Declare a structure named `B` which has a function `test`_28// which has type `fun(): Void`._28//_28struct B {_28 fun test() {}_28}_28_28// Declare a variable named which accepts values of type `A`._28//_28var something: A = A()_28_28// Invalid: Assign a value of type `B` to the variable._28// Even though types `A` and `B` have the same declarations,_28// a function with the same name and type, the types' names differ,_28// so they are not compatible._28//_28something = B()_28_28// Valid: Reassign a new value of type `A`._28//_28something = A()
Composite type behavior
The following describes the behavior of composite types.
Structures
Structures are copied when they are:
- used as an initial value for a constant or variable
- assigned to a different variable
- passed as an argument to a function, and
- returned from a function.
Accessing a field or calling a function of a structure does not copy it.
_30// Declare a structure named `SomeStruct`, with a variable integer field._30//_30access(all)_30struct SomeStruct {_30 _30 access(all)_30 var value: Int_30_30 init(value: Int) {_30 self.value = value_30 }_30_30 fun increment() {_30 self.value = self.value + 1_30 }_30}_30_30// Declare a constant with value of structure type `SomeStruct`._30//_30let a = SomeStruct(value: 0)_30_30// *Copy* the structure value into a new constant._30//_30let b = a_30_30b.value = 1_30// NOTE: `b.value` is 1, `a.value` is *`0`*_30_30b.increment()_30// `b.value` is 2, `a.value` is `0`
Optional chaining
You can access fields and functions of composite types by using optional chaining.
If a composite type with fields and functions is wrapped in an optional, optional chaining can be used to get those values or call the function without having to get the value of the optional first.
Optional chaining is used by adding a ?
before the .
access operator for fields or functions of an optional composite type.
- When getting a field value or calling a function with a return value, the access returns the value as an optional. If the object doesn't exist, the value will always be
nil
. - When calling a function on an optional like this, if the object doesn't exist, nothing will happen and the execution will continue.
It is still invalid to access an undeclared field of an optional composite type:
_22// Declare a struct with a field and method._22access(all)_22struct Value {_22_22 access(all)_22 var number: Int_22_22 init() {_22 self.number = 2_22 }_22_22 access(all)_22 fun set(new: Int) {_22 self.number = new_22 }_22_22 access(all)_22 fun setAndReturn(new: Int): Int {_22 self.number = new_22 return new_22 }_22}
- Create a new instance of the struct as an optional:
_10let value: Value? = Value()
- Create another optional with the same type, but nil:
_10let noValue: Value? = nil
- Access the
number
field using optional chaining:_10let twoOpt = value?.number- Because
value
is an optional,twoOpt
has typeInt?
:
_10let two = twoOpt ?? 0two
is2
.
- Because
- Try to access the
number
field ofnoValue
, which has typeValue?
. This still returns anInt?
:_10let nilValue = noValue?.number- This time, since
noValue
isnil
,nilValue
will also benil
.
- This time, since
- Try to call the
set
function ofvalue
. The function call is performed, asvalue
is not nil:_10value?.set(new: 4) - Try to call the
set
function ofnoValue
. The function call is not performed, asnoValue
is nil:_10noValue?.set(new: 4) - Call the
setAndReturn
function, which returns anInt
. Becausevalue
is an optional, the return value is typeInt?
:_10let sixOpt = value?.setAndReturn(new: 6)_10let six = sixOpt ?? 0six
is6
.
This is also possible by using the force-unwrap operator (!
).
Forced-optional chaining is used by adding a !
before the .
access operator for fields or functions of an optional composite type.
When getting a field value or calling a function with a return value, the access returns the value. If the object doesn't exist, the execution will panic and revert.
It is still invalid to access an undeclared field of an optional composite type:
_22// Declare a struct with a field and method._22access(all)_22struct Value {_22_22 access(all)_22 var number: Int_22_22 init() {_22 self.number = 2_22 }_22_22 access(all)_22 fun set(new: Int) {_22 self.number = new_22 }_22_22 access(all)_22 fun setAndReturn(new: Int): Int {_22 self.number = new_22 return new_22 }_22}
- Create a new instance of the struct as an optional:
_10let value: Value? = Value()
- Create another optional with the same type, but nil:
_10let noValue: Value? = nil
- Access the
number
field using force-optional chaining:_10let two = value!.numbertwo
is2
- Try to access the
number
field ofnoValue
, which has typeValue?
.- Run-time error: This time, since
noValue
isnil
, the program execution will revert.
_10let number = noValue!.number - Run-time error: This time, since
- Call the
set
function of the struct._10value!.set(new: 4)- This succeeds and sets the value to 4
_10noValue!.set(new: 4)- Run-time error: Since
noValue
is nil, the value is not set and the program execution reverts.
- Call the
setAndReturn
function, which returns anInt
. Because we use force-unwrap before calling the function, the return value is typeInt
:_10let six = value!.setAndReturn(new: 6)six
is6
Resources
Resources are explained in detail in this article.
Unbound references and nulls
There is no support for null
.
Inheritance and abstract types
There is no support for inheritance. Inheritance is a feature common in other programming languages, which allows including the fields and functions of one type in another type.
Instead, follow the "composition over inheritance" principle, the idea of composing functionality from multiple individual parts, rather than building an inheritance tree.
Furthermore, there is also no support for abstract types. An abstract type is a feature common in other programming languages, that prevents creating values of the type and only allows the creation of values of a subtype. In addition, abstract types may declare functions, but omit the implementation of them and instead require subtypes to implement them.
Instead, consider using interfaces.