Remove unnecessary functions and implement more APIs: - wasm_##name##same - wasm##name##as_ref - wasm_ref_as##name## - wasm_ref_delete - wasm_module_validate - wasm_table_get/set/size - wasm_memory_size - wasm_config_new - wasm_foreign_new And add more wasm-c-api samples, update the related documen, add more CI rules. Signed-off-by: Wenyong Huang <wenyong.huang@intel.com>
This commit is contained in:
@ -2,9 +2,9 @@
|
||||
|
||||
## Section 1. Guiding Principle
|
||||
|
||||
The WebAssembly Micro Runtime (WAMR) project is part of the
|
||||
Bytecode Alliance (BA) which operates transparently, openly,
|
||||
collaboratively, and ethically. Project proposals, timelines, and status
|
||||
The WebAssembly Micro Runtime (WAMR) project is part of the
|
||||
Bytecode Alliance (BA) which operates transparently, openly,
|
||||
collaboratively, and ethically. Project proposals, timelines, and status
|
||||
must not merely be open, but also easily visible to outsiders.
|
||||
|
||||
## Section 2. Project Governance under Bytecode Alliance
|
||||
@ -17,8 +17,8 @@ there is misalignment between the project charter and the BA mission and values.
|
||||
|
||||
|
||||
|
||||
The PTSC structure described in this document may be overhauled as part of
|
||||
establishing a BA TSC in order to adhere to constraints or requirements that
|
||||
The PTSC structure described in this document may be overhauled as part of
|
||||
establishing a BA TSC in order to adhere to constraints or requirements that
|
||||
TSC will impose on project-level governance.
|
||||
|
||||
## Section 3. Establishment of the PTSC
|
||||
|
||||
Reference in New Issue
Block a user