990: Allow to do wasmer execution without the `run` argument r=MarkMcCaskey a=syrusakbary


# Description
This PR allows Wasmer to run files directly without doing `wasmer run xyz.wasm`.
So you can do `wasmer xyz.wasm`

# Review

- [x] Add a short description of the the change to the CHANGELOG.md file


Co-authored-by: Syrus <me@syrusakbary.com>
Co-authored-by: Mark McCaskey <mark@wasmer.io>
This commit is contained in:
bors[bot] 2019-11-20 23:51:39 +00:00 committed by GitHub
commit 32a8da19d3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 1 deletions

View File

@ -2,6 +2,7 @@
## **[Unreleased]**
- [#990](https://github.com/wasmerio/wasmer/pull/990) Default wasmer CLI to `run`. Wasmer will now attempt to parse unrecognized command line options as if they were applied to the run command: `wasmer mywasm.wasm --dir=.` now works!
- [#987](https://github.com/wasmerio/wasmer/pull/987) Fix `runtime-c-api` header files when compiled by gnuc.
## 0.10.2 - 2019-11-18

View File

@ -848,7 +848,8 @@ fn get_compiler_by_backend(backend: Backend) -> Option<Box<dyn Compiler>> {
}
fn main() {
let options = CLIOptions::from_args();
let options = CLIOptions::from_iter_safe(env::args())
.unwrap_or_else(|_| CLIOptions::Run(Run::from_args()));
match options {
CLIOptions::Run(options) => run(options),
#[cfg(not(target_os = "windows"))]