From 3c2360eade742c1ea754dbeb36fbf85aad20b150 Mon Sep 17 00:00:00 2001 From: boneyard93501 Date: Fri, 11 Jun 2021 01:48:13 +0000 Subject: [PATCH] GitBook: [main] 54 pages modified --- knowledge_knowledge/knowledge_aquamarine/hll.md | 2 +- .../knowledge_aquamarine/knowledge_aquamarine_air.md | 2 +- .../knowledge_aquamarine/marine/marine-rs-sdk.md | 4 +--- knowledge_knowledge/knowledge_aquamarine/vm.md | 2 +- 4 files changed, 4 insertions(+), 6 deletions(-) diff --git a/knowledge_knowledge/knowledge_aquamarine/hll.md b/knowledge_knowledge/knowledge_aquamarine/hll.md index 6740663..630f2b9 100644 --- a/knowledge_knowledge/knowledge_aquamarine/hll.md +++ b/knowledge_knowledge/knowledge_aquamarine/hll.md @@ -1,4 +1,4 @@ -# HLL +# Aqua ## Aquamarine High Level Language diff --git a/knowledge_knowledge/knowledge_aquamarine/knowledge_aquamarine_air.md b/knowledge_knowledge/knowledge_aquamarine/knowledge_aquamarine_air.md index 6dea06b..25b942b 100644 --- a/knowledge_knowledge/knowledge_aquamarine/knowledge_aquamarine_air.md +++ b/knowledge_knowledge/knowledge_aquamarine/knowledge_aquamarine_air.md @@ -23,7 +23,7 @@ AIR instructions are intended to launch the execution of a service method as fol 4. The arguments specified by the argument list are passed to the method 5. The result of the method returned under the name output name -**Figure 2: Sequential Instruction** ![Execution](../../.gitbook/assets/air_sequential_2%20%281%29%20%281%29%20%281%29%20%281%29%20%281%29%20%282%29%20%283%29%20%282%29.png) +**Figure 2: Sequential Instruction** ![Execution](../../.gitbook/assets/air_sequential_2%20%281%29%20%281%29%20%281%29%20%281%29%20%281%29%20%282%29%20%283%29%20%284%29%20%282%29.png) The _**seq**_ instruction takes two instructions at most as its arguments and executes them sequentially, one after the other. diff --git a/knowledge_knowledge/knowledge_aquamarine/marine/marine-rs-sdk.md b/knowledge_knowledge/knowledge_aquamarine/marine/marine-rs-sdk.md index 1936bf1..efd0440 100644 --- a/knowledge_knowledge/knowledge_aquamarine/marine/marine-rs-sdk.md +++ b/knowledge_knowledge/knowledge_aquamarine/marine/marine-rs-sdk.md @@ -201,7 +201,7 @@ Please not that if you want to use `curl_request` with testing, see below, the c since cargo does not have access to the magic in place in the marine rs sdk to handle unsafe. -MountedBinaryResult itself is a Marine-compatible struct containing a binary's return process code, error string, stdout and stderr: +MountedBinaryResult itself is a Marine-compatible struct containing a binary's return process code, error string and stdout and stderr as byte arrays: ```rust #[marine] @@ -224,8 +224,6 @@ pub struct MountedBinaryResult { MountedBinaryResult then can be used on a variety of match or conditional tests. - - #### Testing Since we are compiling to a wasm32-wasi target with `ftype` constrains, the basic `cargo test` is not all that useful or even usable for our purposes. To alleviate that limitation, Fluence has introduced the [`[marine-test]` macro ](https://github.com/fluencelabs/marine-rs-sdk/tree/master/crates/marine-test-macro)that does a lot of the heavy lifting to allow developers to use `cargo test` as intended. That is, `[marine-test]` macro generates the necessary code to call Marine, one instance per test function, based on the Wasm module and associated configuration file so that the actual test function is run against the Wasm module not the native code. diff --git a/knowledge_knowledge/knowledge_aquamarine/vm.md b/knowledge_knowledge/knowledge_aquamarine/vm.md index aaded61..ec6c770 100644 --- a/knowledge_knowledge/knowledge_aquamarine/vm.md +++ b/knowledge_knowledge/knowledge_aquamarine/vm.md @@ -1,2 +1,2 @@ -# VM +# Aqua VM