Our pain point is “change one line in the script crate, observe the long cycle time”. Bazel would not help us with that. Compiler improvements would.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
Replying to @BRIAN_____ @sayrer
It was never a design goal to cache tests. I can certainly see the value of adding that feature to Cargo and/or adding Bazel integration so Bazel can do it. It hasn’t been high priority thus far because e.g. incremental compilation has been a more frequent feature request.
0 replies
1 retweet
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.