Added invoke option to the command

[syrusakbary]

Description

This PR adds an --invoke to the Wasmer CLI

Review

• Add a short description of the the change to the CHANGELOG.md file

[nlewycky]

Why invoke and not -e for entry?

[nlewycky]

Maybe "specify the name of the start function" or "of the main function" of something like that?

[syrusakbary]

Is not a main function, but a raw function that you might want to invoke.

[bjfish]

It would be nice if this could take integer parameters like --invoke fun_name 2,3,4 ... this was also previously suggested to be a separate command wasmer invoke fun_name 2,3,4, and to print the result.

[syrusakbary]

@nlewycky

Why invoke and not -e for entry?

It's not an entry function. But a function that you might want to call it alone. In general I'm following the naming of other implementations

@bjfish

It would be nice if this could take integer parameters like --invoke fun_name 2,3,4 ... this was also previously suggested to be a separate command wasmer invoke fun_name 2,3,4, and to print the result.

Right now it will take the arguments provided in the CLI (transformed to the necessary i32, i64, ... values). Such as:

wasmer run myfile.wasm --invoke fun 1 2 3

[MarkMcCaskey]

⛳️

Consider:

#[structopt(long = "invoke", short = "i", default = "main")]
invoke: String

This is less flexible, but for the code as it is now, this is a cleaner solution

[syrusakbary]

I don't like that much, because depending on the integration you use (emscripten, wasi, ...) the default might vary. Will go through the other approach

[syrusakbary]

bors r+

[bors]

Build succeeded

• wasmerio.wasmer