A WASM module can export entities, like functions, memories, globals and tables. This example illustrates how to use exported globals.
In this example we'll be using a simple WASM module which exports some globals.
Globals are probably the simplest entity we'll encounter in WASM modules but there is still some interesting things to talk about. For example, globals come in two flavors:
Immutable globals (const)
Mutable globals (var)
We will cover both in this example.
First we are going to want to initialize a new project. To do this we can navigate to our project folder, or create one. In this example, we will create a new project. Lets create it and navigate to it:
The final code for this example can be found on GitHub.
Now that we have everything set up, let's go ahead and try it out!
Querying types information
The first interesting thing to do is to query their type information in order to know if they are mutable or not. Our module exports two globals, one and some. Which one is mutable and which one is not?
The global API is straightforward: it provides a dedicated method to get the value of a given global. Look how easy it is:
let some_value = some.get();println!("`some` value: {:?}", some_value);
someValue, err := some.Get()if err !=nil {panic(fmt.Sprintln("Failed to get the `some` global value:", err))}fmt.Printf("`some` value: %.1f\n", someValue)
We now have everything we need to run the WASM module, let's do it!
You should be able to run it using the cargo run command. The output should look like this:
Compiling module...
Instantiating module...
Getting globals types information...
`one` type: Const F32
`some` type: Var F32
Getting global values...
`one` value: 1.0
`some` value: F32(0.0)
Setting global values...
`one` value after `set`: F32(1.0)
`some` value after `set_some`: F32(21.0)
`some` value after `set`: F32(42.0)
If you want to run the examples from the Wasmer repository codebase directly, you can also do: