3 ms·
Be aware that this article is by now over a year old. While I respect him a lot for a lot of the work he does some of the thinks in that article are IMHO just
by dathinab 6y ago
Be aware that this article is by now over a year old.
While I respect him a lot for a lot of the work he does some of the thinks in that article are IMHO just not right (and hadn't been a year ago either).
E.g. yes cargo is somewhat mandatory but no rust doesn't refuses to play along. It's just that if you try to integrate rustc in the same way you would do so for a C/C++ compiler it wouldn't work because they way rust build thinks it's very different. So the best way to integrate rust into another build system is through cargo, which had been extended with such and other use cases in mind (emitting metadata etc.).
Also in practice you often have similar problems for C/C++ projects which requires you to use that specific build system or port and maintain houndred of lines of <make/python/..> code. Worse the isn't a standard way to do thinks like running tests or seeing which features so exist.