SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
SoylentNews
After many years of waiting, version 1.0 of the Rust programming language has finally been released. The Rust home page describes Rust as "a systems programming language that runs blazingly fast, prevents nearly all segfaults, and guarantees thread safety."
Thanks to the hard work of noted Rust core team members Yehuda Katz and Steve Klabnik, Rust is now poised to become a serious competitor to established systems programming languages like C and C++.
The announcement has brought much jubilation to the followers of Rust, who have been eagerly awaiting this milestone release for so long. With only 1,940 open issues and over 11,500 issues already closed, Rust is finally ready for users to build fantastically reliable software systems using it.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
The last time I saw him he was walking down Lover's Lane holding his own hand.
-- Fred Allen
(Score: 4, Insightful) by maxwell demon on Saturday May 16 2015, @07:22AM
I disagree with this. It shows on many places that the C syntax on which it builds simply wasn't made for it, and some added syntax also is not exactly helpful.
Consider the following code, and think about why you need the bolded keywords:
template<typename T, typename U> typename T::value_type f(T t, U u)
{
T foo(U()); // C++'s most vexing parse; do you see what's wrong?
return foo.template frobnicate<int>(u);
}
Don't get me wrong, C++ is the best language I know. But its syntax is not its strong point.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2) by tonyPick on Saturday May 16 2015, @08:01AM
Templates can lead to some really odd cases: See also this blog post [reverberate.org].
Responding to the GP point: C++ syntax can be straightforward provided you only use a subset of the features; however nobody can agree on what that subset is, and as soon as you use someone else's code/library then the complexity explodes. The C++ standards approach of "throw another feature into the mix" isn't helping any.