Skip to content
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

Incorrect caching of expr #64

Open
scooter-dangle opened this issue Nov 19, 2018 · 0 comments
Open

Incorrect caching of expr #64

scooter-dangle opened this issue Nov 19, 2018 · 0 comments

Comments

@scooter-dangle
Copy link

When re-running a script supplied via the --expr flag, cargo script will often return the most recent of any cached results rather than the result of the actual argument.

(The following example starts in fish. Switches to bash in case fish was doing something odd.)

~/s/r/cargo-script (master|✔)> cargo script --expr '2 + 3'
   Compiling expr v0.1.0 (/Users/scott/.cargo/script-cache/expr-159ccec4a4d6f466)
    Finished release [optimized] target(s) in 2.02s
5
~/s/r/cargo-script (master|✔)> cargo script --expr '2 + 2'
4
~/s/r/cargo-script (master|✔)> cargo script --expr '2 + 3'
4
~/s/r/cargo-script (master|✔)> bash
bash-3.2$ which cargo
/Users/scott/.cargo/bin/cargo
bash-3.2$ cargo script --expr '2 + 3'
4
bash-3.2$ cargo script --expr '2 + 2'
4
bash-3.2$ cargo script --expr '2 + 1'
3
bash-3.2$ cargo script --expr '2 + 3'
3

Installed via cargo install --force (had previously installed both 2.7 and 2.8) from master:

~/s/r/cargo-script (master|✔)> git rev-parse HEAD
614e60e5932e218ebff1e471303eb0d59870d03b

Re-verified the behavior after running cargo script --clear-cache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant