News for hackers. Stuff that matters.

ecl3ctic

Re:Nvidia announces native GPU programming in Rust on Wednesday September 16, 2026 @07:12PM (#49734305)
The Mojo compiler has been open source for over a month now.

And the Mojo standard library has been open source for over a year.

It’s all open source. Go check it out!

Re:Let's remove Quaternions from every 3D Engine on Friday November 02, 2018 @09:04PM (#18368036)
Please do blog about this. I'd be really interested to hear your thoughts!
Re:Rust Guide on Saturday September 13, 2014 @09:14PM (#8314225)
I know you're not exactly opposing the above comment, but I'll make a supporting argument here which acknowledges what you've said:

I feel as though we can retain understanding of those differences without using the name "Vec", which can be considered a poor choice for the reasons mentioned above (by C++ and Rust alike).

Array<T> for a growable array

[T, ..N] for a fixed-length array

&[T] for a slice into either of these array types

Even forgetting the mathematical concept, I would argue that throwing the term "Vector" into the mix only makes things more complicated than they need to be, since sticking to "Array" homogenizes everything. For good reason, we don't call a resizable string a "Hobnob" in an attempt to disambiguate, so why call a resizable array a "Vector", which makes just as much sense?