I don’t recall ease-of-use as part of the pitch to me either, I have to say. It’s great, but only once it’s off the ground enough that people _want_ to use it. EOU promotes adoption, and you don’t want a lot of 0.1 adoption anyway IMO.
-
-
How is the build system supposed to know? Does Bazel have a magic Rust parser that can understand comment changes?
- 10 more replies
New conversation -
-
-
Once that work is done, getting the build system to take advantage of this information is the easy part. It could be solved with Bazel, but it would be a lot less work to just solve it in rustbuild.
-
But unless this work is done in the compiler—which is the hard part—switching to Bazel will do nothing to help.
- 1 more reply
New conversation -
-
-
Why can’t the build system look at the pending inputs and cached outputs and avoid even asking the compiler in the first place. With the FB Android app, if you ran javac you’d already lost, so to get real wins you have to avoid running the compiler, aggressively.
-
The build system sees a .rs file change. That change could potentially invalidate everything. It would have to be able to parse Rust to know that it’s a comment change.
- 2 more replies
New conversation -
-
This Tweet is unavailable.
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.