cargo-watch
cargo-watch copied to clipboard
`cargo watch` in a workspace root gets triggered by the updated `Cargo.lock`
Running cargo watch
in a workspace root gets triggered by the updated Cargo.lock
file. This creates an infinite loop.
I have verified this by running cargo watch --why
in a skeleton workspace.
I'm also interested in looking into this, if I can get some tips where to start.
I mean I guess that's really not a bug, right now. With --watch-when-idle
it will stop restarting the process on file change immediately. That will probably become the default in 9.0