zach 360df45e1a fix: require modules to have exported, bounded memory when manifest memory.max_pages field is set (#356) ...

- Requires modules compiled to run with manifests that set `max_memory`
to have an exported memory with lower and upper bounds
- Includes the size of memory exported from modules when calculating
available memory for plugins

## How to compile a module with bounded memory 

You will need to pass `--max-memory=$NUM_BYTES` to wasm-ld. `$NUM_BYTES`
must be a multiple of the page size. Here are some examples for
supported PDK languages:

**C** 
Pass `-Wl,--max-memory=65536` to your C compiler

**Rust**: 
In a `.cargo/config` file:
```toml
[target.wasm32-unknown-unknown]
rustflags = ["-Clink-args=--max-memory=65536"]
 ```
**Haskell**
Add the following to the cabal file entry for your `cabal.project` file:

```
package myproject
  ghc-options:
    -optl -Wl,--max-memory=65536
```
**AssemblyScript**
Pass `--maximumMemory 65536` to the assemblyscropt compiler

**TinyGo**:
Create a `target.json` file:
```json
{
    "inherits": [ "wasm" ],
    "ldflags": [
        "--max-memory=65536",
    ]
}
```
and build using `tinygo -target ./target.json`

2023-06-01 09:37:42 -07:00

..

example

fix: require modules to have exported, bounded memory when manifest memory.max_pages field is set (#356)

2023-06-01 09:37:42 -07:00

src

feat(php): Implicit context (#347)

2023-05-18 15:59:17 -05:00

.gitignore

feat: add extism_plugin_update (#6)

2022-09-09 00:39:57 -06:00