Composite Types
Composite types allow composing simpler types into more complex types, i.e., 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. The kinds differ in their usage and the behaviour when a value is used as the initial value for a constant or variable, when the value is assigned to a variable, when the value is passed as an argument to a function, and when the value is returned from a function:
-
Structures are copied, they are value types.
Structures are useful when copies with 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).
Certain constructs in a blockchain represent assets of real, tangible value, as much as a house or car or bank account. We have to worry about 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 are 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.
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.
_10pub struct SomeStruct {_10 // ..._10}_10_10pub resource 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.
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 three 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
letkeyword. -
Variable fields are stored in the composite value and can have new values assigned to them.
Variable fields are declared using the
varkeyword.
| 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 its field types must be storable. Non-storable types are:
- Functions
- Accounts (
AuthAccount/PublicAccount) - 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.
_19// Declare a structure named `Token`, which has a constant field_19// named `id` and a variable field named `balance`._19//_19// Both fields are initialized through the initializer._19//_19// The public access modifier `pub` is used in this example to allow_19// the fields to be read in outer scopes. Fields can also be declared_19// private so they cannot be accessed in outer scopes._19// Access control will be explained in a later section._19//_19pub struct Token {_19 pub let id: Int_19 pub var balance: Int_19_19 init(id: Int, balance: Int) {_19 self.id = id_19 self.balance = balance_19 }_19}
Note that it is invalid to provide the initial value for a field in the field declaration.
_10pub struct 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 pub let id: Int = 1_10}
The field access syntax must be used to access fields – fields are not available as variables.
_10pub struct Token {_10 pub let id: Int_10_10 init(initialID: Int) {_10 // Invalid: There is no variable with the name `id` available._10 // The field `id` must be initialized by setting `self.id`._10 //_10 id = initialID_10 }_10}
The initializer is not automatically derived from the fields, it must be explicitly declared.
_10pub struct Token {_10 pub 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.
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.
_25// Declare a structure named "Rectangle", which represents a rectangle_25// and has variable fields for the width and height._25//_25pub struct Rectangle {_25 pub var width: Int_25 pub var height: Int_25_25 init(width: Int, height: Int) {_25 self.width = width_25 self.height = height_25 }_25_25 // Declare a function named "scale", which scales_25 // the rectangle by the given factor._25 //_25 pub fun scale(factor: Int) {_25 self.width = self.width * factor_25 self.height = self.height * factor_25 }_25}_25_25let rectangle = Rectangle(width: 2, height: 3)_25rectangle.scale(factor: 4)_25// `rectangle.width` is `8`_25// `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 `((): Void)`._28//_28struct A {_28 fun test() {}_28}_28_28// Declare a structure named `B` which has a function `test`_28// which has type `((): 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 Behaviour
Structures
Structures are copied when used as an initial value for constant or variable, when assigned to a different variable, when passed as an argument to a function, and when returned from a function.
Accessing a field or calling a function of a structure does not copy it.
_27// Declare a structure named `SomeStruct`, with a variable integer field._27//_27pub struct SomeStruct {_27 pub var value: Int_27_27 init(value: Int) {_27 self.value = value_27 }_27_27 fun increment() {_27 self.value = self.value + 1_27 }_27}_27_27// Declare a constant with value of structure type `SomeStruct`._27//_27let a = SomeStruct(value: 0)_27_27// *Copy* the structure value into a new constant._27//_27let b = a_27_27b.value = 1_27// NOTE: `b.value` is 1, `a.value` is *`0`*_27_27b.increment()_27// `b.value` is 2, `a.value` is `0`
Accessing Fields and Functions of Composite Types 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.
_47// Declare a struct with a field and method._47pub struct Value {_47 pub var number: Int_47_47 init() {_47 self.number = 2_47 }_47_47 pub fun set(new: Int) {_47 self.number = new_47 }_47_47 pub fun setAndReturn(new: Int): Int {_47 self.number = new_47 return new_47 }_47}_47_47// Create a new instance of the struct as an optional_47let value: Value? = Value()_47// Create another optional with the same type, but nil_47let noValue: Value? = nil_47_47// Access the `number` field using optional chaining_47let twoOpt = value?.number_47// Because `value` is an optional, `twoOpt` has type `Int?`_47let two = twoOpt ?? 0_47// `two` is `2`_47_47// Try to access the `number` field of `noValue`, which has type `Value?`._47// This still returns an `Int?`_47let nilValue = noValue?.number_47// This time, since `noValue` is `nil`, `nilValue` will also be `nil`_47_47// Try to call the `set` function of `value`._47// The function call is performed, as `value` is not nil_47value?.set(new: 4)_47_47// Try to call the `set` function of `noValue`._47// The function call is *not* performed, as `noValue` is nil_47noValue?.set(new: 4)_47_47// Call the `setAndReturn` function, which returns an `Int`._47// Because `value` is an optional, the return value is type `Int?`_47let sixOpt = value?.setAndReturn(new: 6)_47let six = sixOpt ?? 0_47// `six` is `6`
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.
_46// Declare a struct with a field and method._46pub struct Value {_46 pub var number: Int_46_46 init() {_46 self.number = 2_46 }_46_46 pub fun set(new: Int) {_46 self.number = new_46 }_46_46 pub fun setAndReturn(new: Int): Int {_46 self.number = new_46 return new_46 }_46}_46_46// Create a new instance of the struct as an optional_46let value: Value? = Value()_46// Create another optional with the same type, but nil_46let noValue: Value? = nil_46_46// Access the `number` field using force-optional chaining_46let two = value!.number_46// `two` is `2`_46_46// Try to access the `number` field of `noValue`, which has type `Value?`_46// Run-time error: This time, since `noValue` is `nil`,_46// the program execution will revert_46let number = noValue!.number_46_46// Call the `set` function of the struct_46_46// This succeeds and sets the value to 4_46value!.set(new: 4)_46_46// Run-time error: Since `noValue` is nil, the value is not set_46// and the program execution reverts._46noValue!.set(new: 4)_46_46// Call the `setAndReturn` function, which returns an `Int`_46// Because we use force-unwrap before calling the function,_46// the return value is type `Int`_46let six = value!.setAndReturn(new: 6)_46// `six` is `6`
Resources
Resources are explained in detail in the following page.
Unbound References / 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, that 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.