-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
evalrs -h
doesn't work
#1
Comments
Thank you for reaching out. |
Hmm, in my environment (rustc-1.46.0, WSL2), it worked as expected. $ cargo install -f evalrs
Updating crates.io index
Downloaded evalrs v0.0.11
Downloaded 1 crate (4.6 KB) in 1.49s
Installing evalrs v0.0.11
Downloaded libc v0.2.79
Downloaded 1 crate (511.8 KB) in 1.04s
Compiling libc v0.2.79
Compiling memchr v2.3.3
Compiling bitflags v1.2.1
Compiling unicode-width v0.1.8
Compiling lazy_static v1.4.0
Compiling vec_map v0.8.2
Compiling strsim v0.8.0
Compiling remove_dir_all v0.5.3
Compiling ansi_term v0.11.0
Compiling regex-syntax v0.6.18
Compiling textwrap v0.11.0
Compiling thread_local v1.0.1
Compiling aho-corasick v0.7.13
Compiling atty v0.2.14
Compiling rand v0.4.6
Compiling clap v2.33.3
Compiling tempdir v0.3.7
Compiling regex v1.3.9
Compiling evalrs v0.0.11
Finished release [optimized] target(s) in 33.71s
Replacing /home/ohta/.cargo/bin/evalrs
Replaced package `evalrs v0.0.11` with `evalrs v0.0.11` (executable `evalrs`)
$ evalrs -h
evalrs 0.0.11
Takeru Ohta <[email protected]>
A Rust code snippet evaluator
USAGE:
evalrs [FLAGS] [SNIPPET]
FLAGS:
-p, --print-result Prints the evaluation result using `println!("{:?}", result)`
-q, --quiet Don't show cargo's build messages if succeeded
--release Builds artifacts in release mode, with optimizations
-h, --help Prints help information
-V, --version Prints version information
ARGS:
<SNIPPET> Rust code snippet to be evaluated. If this is omitted, the snippet will be read from the standard
input. Could you give me more information to reproduce your result? |
I'm on Gentoo GNU/Linux
|
Whoops, sorry for the issue, I've just checked my PATH and it looks like that's where the problem was. PEBKAC, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's used in
README.md
as an example, but it doesn't seem to produce any output.Compiled with:
The text was updated successfully, but these errors were encountered: