On: Cross-platform Rust Rewrite of the GNU Coreutils

[steveklabnik]

I am a performance noob, but given that fortran can be faster than C due to increased information about aliasing, and given how much more aliasing information Rust has, I don't see why Rust couldn't eventually even beat C on certain kinds of things. (And obviously, aliasing is only a tiny part of performance, just something that comes to mind.)

That said, I am FAR more concerned about shipping a solid 1.0 than on a maximum performance one. It'll be a while, but we'll get there.

[idbfs → steveklabnik]

A nitpick: C has been able to achieve the same performance as Fortran since C99 introduced the "restrict" keyword.

[steveklabnik → idbfs]

I was reading the other day that Windows doesn't really support most of C99, is restrict part of that or not?

[ygra → steveklabnik]

Visual Studio ships only with a C++ compiler. That doesn't mean you cannot use other C compilers on Windows.

Still, there seems to be something similar since VS2005. »__restrict is similar to restrict from the C99 spec, but __restrict can be used in C++ or C programs.«: http://msdn.microsoft.com/library/5ft82fed.aspx

[fithisux → ygra]

PellesC has a new release candidate. LCC-WIN32 (compatible with what standard???) has a steady stream of releases. Openwatcom v2 has also changes. VS is only good for VisualD.

[steveklabnik → ygra]

Ugh, yes, I should have said "MSVC++," or "Microsoft." Thank you.

[hornetblack → steveklabnik]

MS specifically implemented __restrict:

> __restrict is similar to restrict from the C99 spec, but __restrict can be used in C++ or C programs.

http://msdn.microsoft.com/en-us/library/5ft82fed.aspx

[ternaryoperator → steveklabnik]

As of VS2013, MS supports almost the entire C99 spec.