en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/cli_tests/run#80915565 Require wasmtime options are first when running modules (#6737)* Require wasmtime options are first when running modulesCurrently the way we've configured argument parsing it's valid toexecute a command such as: wasmtime run foo.wasm -Owhich is the same as: wasmtime run -O foo.wasmor otherwise all flags are attempted to be parsed as Wasmtime flags andan error is generated when they're not wasmtime flags. I've personallyfound this a bit confusing in the past and I find myself frequentlyexecuting: wasmtime run -- foo.wasm -other -argumentsWhile this works my general impression is that many other "wrappercommands" don't behave this way and typically don't require `--` to passflags to the target executable. This commit reconfigures argumentparsing to consider any argument after the WebAssembly module itself tobe an argument to the wasm program rather than an argument to Wasmtime.This means that all Wasmtime options must come between the `run` commandand the `foo.wasm` WebAssembly argument.* Update wasi testsuite runner* Support `wasmtime -- run`Additionally use more clap features to avoid manually checking againstsubcommands.* Remove stale comment* Reorder wasi-nn arguments* Reorder more flags* Fix unused import on Windows* Don't run a stdio test on Windows* Update gdb/lldb tests* Don't assert that the write succeedsprtest:full List of files: /wasmtime-44.0.1/tests/all/cli_tests/run Thu, 20 Jul 2023 13:24:35 +0000 Alex Crichton <alex@alexcrichton.com>