#rust2019
I'm a simple person. I want faster compilations and features to stabilize.
I don't want big changes that cause my team to freak out about instability. I also don't want increased dependence on cargo. I like cargo, I just work on a project that *can not* use it.
Out of curiosity: what are the maon reasons Cargo can't be used? Are they technical, or is it more policy-oriented?
-
-
*main reasons, oops
-
A small bit of policy, but mostly technical. We compile a lot of C++ at the same time. We tried to integrate cargo with GN for a while, but it was a poor fit. Cargo really wants to be driving the whole build. Making rust GN rules has been a huge win
- 1 more reply
New conversation -
-
-
Large projects typically have their own build toolchains for very valid reasons, and can't really work well with tools that want to control the entire build process like cargo. This is pretty typical.
-
Like, the solutions end up being "somehow rewrite the non-rust build steps as a build script and make it one monster rust project" vs "don't use cargo" and projects will choose the latter every time
- 9 more replies
New conversation -
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.