News for hackers. Stuff that matters.

A comment on The internals of testing in Rust in 2018. Parent comment

Re:The internals of testing in Rust in 2018 by fnord123 on Tuesday July 24, 2018 @05:30AM (#17599354)
I think cargo supporting binaries and sharing build dependencies between projects (cf maven's .m2 directory) will mitigate a /lot/ of Rust's build time issues.
[ Parent | on HN ]
Re:The internals of testing in Rust in 2018 by steveklabnik on Tuesday July 24, 2018 @09:32AM (#17600802)
That only helps on the first build, really.
[ Parent | on HN ]
Re:The internals of testing in Rust in 2018 by fnord123 on Tuesday July 24, 2018 @09:57AM (#17601014)
It brings the cost of trying an idea out down considerably. I've had a few times where I think "i know, I'll just try this idea out" and then I make a new project, add a few deps in Cargo.toml, hack some code, and then build. Oops, the first build takes half an hour. Then I think I should try new ideas out in Go or python. Alas.
[ Parent | on HN ]
Re:The internals of testing in Rust in 2018 by steveklabnik on Tuesday July 24, 2018 @02:01PM (#17603491)
That’s fair!
[ Parent | on HN ]
Re:The internals of testing in Rust in 2018 by fnord123 on Sunday July 29, 2018 @04:05AM (#17637059)
Also CI builds...
[ Parent | on HN ]