mirror of
https://github.com/fluencelabs/aquavm
synced 2025-04-24 14:52:15 +00:00
chore: fix typos (#704)
This commit is contained in:
parent
8f23d90ece
commit
8013e5e8f8
@ -36,7 +36,7 @@ handle the future response, see Figure 2.
|
|||||||
**Figure 2: AquaVM Interpreter Execution Model**
|
**Figure 2: AquaVM Interpreter Execution Model**
|
||||||
|
|
||||||
In summary, the AquaVM execution model handles the topological hops for simple
|
In summary, the AquaVM execution model handles the topological hops for simple
|
||||||
and advanced composition patters, such as (async) parallel service execution on
|
and advanced composition patterns, such as (async) parallel service execution on
|
||||||
one or multiple peers.
|
one or multiple peers.
|
||||||
|
|
||||||
## Aquamarine Intermediate Representation (AIR): IR for P2P Systems
|
## Aquamarine Intermediate Representation (AIR): IR for P2P Systems
|
||||||
|
@ -10,7 +10,7 @@
|
|||||||
- the peer is expected to host Wasm service with the specified `service name`
|
- the peer is expected to host Wasm service with the specified `service name`
|
||||||
- the `service function` is expected to contain the specified function
|
- the `service function` is expected to contain the specified function
|
||||||
- the `arguments list` is given to the function and may be empty
|
- the `arguments list` is given to the function and may be empty
|
||||||
- the result of the function execution is saved and returned by it's `output name`
|
- the result of the function execution is saved and returned by its `output name`
|
||||||
|
|
||||||
Example:
|
Example:
|
||||||
```wasm
|
```wasm
|
||||||
@ -208,10 +208,10 @@ Example
|
|||||||
### Canonicalized streams and stream-based maps
|
### Canonicalized streams and stream-based maps
|
||||||
|
|
||||||
- contains an array of elements that was in a stream or a map at the moment of canonicalization
|
- contains an array of elements that was in a stream or a map at the moment of canonicalization
|
||||||
- canonicalized streams or maps are imutable and fully consistent as scalars
|
- canonicalized streams or maps are immutable and fully consistent as scalars
|
||||||
- has the same algebra as a stream for `match`/`mismatch` and `call` argument
|
- has the same algebra as a stream for `match`/`mismatch` and `call` argument
|
||||||
- has the same algebra as a scalar for `new`
|
- has the same algebra as a scalar for `new`
|
||||||
- has mixed behaviour for with other instructions
|
- has mixed behaviour for with other instructions
|
||||||
- can be a target for a lens(previously known as lambda paths)
|
- can be a target for a lens(previously known as lambda paths)
|
||||||
- maps has an additional index access operation that returns a canon stream.
|
- maps has an additional index access operation that returns a canon stream.
|
||||||
- maps index access syntax leverages lens syntax, .e.g `#%canon_map.$.key_name`
|
- maps index access syntax leverages lens syntax, e.g. `#%canon_map.$.key_name`
|
||||||
|
@ -31,4 +31,4 @@ This variable represents the current version of an interpreter data format, it a
|
|||||||
|
|
||||||
## AVM updating policy
|
## AVM updating policy
|
||||||
|
|
||||||
Both `AVM client` and `AVM server` versions should be updated simultaniously in case of breaking change in `AquaVM core` interface, e.g., when arguments are changes. Often they must be updated if `Interpreter interface` crate was changed, but they not need to be updated if `Interpreter data` or `AquaVM core` itself was changed.
|
Both `AVM client` and `AVM server` versions should be updated simultaneously in case of breaking change in `AquaVM core` interface, e.g., when arguments are changes. Often they must be updated if `Interpreter interface` crate was changed, but they don't need to be updated if `Interpreter data` or `AquaVM core` itself was changed.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user