Linked by Thom Holwerda on Thu 21st Jun 2018 22:49 UTC
General Development

Rust 1.27.0 has been released! As regular readers will know, I'm not a programmer and know very little about the two main new features in this release. The biggest new feature is SIMD.

Okay, now for the big news: the basics of SIMD are now available! SIMD stands for "single instruction, multiple data".

The detailed release notes have more information.

Thread beginning with comment 658919
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Too many build systems
by teco.sb on Fri 22nd Jun 2018 21:10 UTC in reply to "RE[3]: Too many build systems"
teco.sb
Member since:
2014-05-08

And GNU didn't have to code the GCC compiler in C ? There are actually very good reasons for that, from dogfooding to the fact that writing something in Rust gives more assurances and productivity than writing it in C.

Your argument would be valid if a C compiler was not a standard tool, as described by the POSIX specification. See cc(1), for more info. Even today, GCC does not use non-standard C exactly so that it can be compiled by other C compilers. Additionally, C compilers used to be coded in assembly, and even in other languages, when a C compiler was not a standard tool. This particular argument is completely invalid.

Concerning the build system, there are numerous systems that the devs could have chosen. I point you to: https://en.wikipedia.org/wiki/List_of_build_automation_software

You/They should have a really good reason why yet another, incompatible with current offering, should be created. Additionally, as a system language, the Rust build system should not be dependent on anything other than the standard system tools. What makes their build system so special that a ./configure && make && make install not possible

Reply Parent Score: 3

RE[5]: Too many build systems
by moltonel on Fri 22nd Jun 2018 23:50 in reply to "RE[4]: Too many build systems"
moltonel Member since:
2006-02-24

Really, the fact that CC is described by POSIX or commonly available is irrelevant. As long as you can get your software on the system, it doesn't matter which door it came thru.

Asking that every language should be bootstrappable from C is very narrow-minded. Some People have high ambitions for Rust, that it'll displace C/C++ in the many areas that they still dominate. Rust being written in C would kill its credibility in that respect. Rust tools are written in Rust because the language is believed to be superior.

I've already why writing cargo was worth it, and why compiling cargo with cargo made sense (I hadn't mentioned Windows support though: you don't want to have to `./configure && make` on that platform).

You link to a big list of build systems, don't you wonder why there are so many, instead of everybody simply using make ? The Rust team wasn't allowed to add to that list ?

Cargo is not incompatible with current offerings, it can be incorporated into an existing build system, just to build the bits that want to be built with cargo.

Cargo is not just a build system : it handles dependency tracking, fetching, updating, it tests, benchmarks, generates docs, releases, analyzes. It is ergonomically integrated with Rust. It'll take over the functionalities of rustup. It is a great tool that I'd love to have in other languages.

Reply Parent Score: 2