Are there any plans for ARM-support? Last time I looked, it did not seem to be supported.
I have written rust programs targeting ARM without any difficulties in the past few months. Both running as linux userland and bare metal.
Announcing Rust 1.0 Alpha
71–80 of 255 posts
Re: Announcing Rust 1.0 Alpha
#72Are there any plans for ARM-support? Last time I looked, it did not seem to be supported.
ARM is well supported, and has been for quite some time. Where did you read that there was no ARM support?
I attempted to install Rust on my ODROID-XU3 (which is running Lubuntu 14.04.1 LTS) just now by running:
curl -s https://static.rust-lang.org/rustup.sh | sudo sh
rustup: CFG_CURL := /usr/bin/curl (7.35.0)
rustup: CFG_TAR := /bin/tar (1.27.1)
rustup: CFG_FILE := /usr/bin/file (5.14)
rustup: CFG_SHA256SUM := /usr/bin/sha256sum (256sum)
rustup: CFG_SHASUM := /usr/bin/shasum (5.84)
rustup:
rustup: processing sh args
rustup:
rustup: CFG_PREFIX :=
rustup: CFG_DATE :=
rustup:
rustup: validating sh args
rustup:
rustup: error: unknown CPU type: armv7l
Re: Announcing Rust 1.0 Alpha
#73Earlier quoted context omitted.
Finally! I hadn't used Rust for two weeks, and when I downloaded the nightly last night, code from two weeks ago was breaking. Feature stability will help.
Oh, and what's the matching version of Cargo? Is Cargo still changing so rapidly that it needs to be downloaded nightly?
You get a Cargo when you install Rust.
Re: Announcing Rust 1.0 Alpha
#74The one thing that would put rust over the top right now is something along the lines of gofmt - something simple, with zero configuration, that can be run on commit or even save.
We absolutely want one, but we've been actually developing the conventions first. You have to know what you want to format to!
Re: Announcing Rust 1.0 Alpha
#75Earlier quoted context omitted.
Core team member here. The standard library is _not_ "batteries included," on purpose. Given that we have Cargo, and it works well, tying package updates to the language version has quite a bit of downside, and very little upside. That said, the Rust team itself maintains and provides a number of packages on Crates.io ourselves. Many of these were pulled _out_ of the standard library over the past few months.
> The standard library is _not_ "batteries included," on purpose. Given that we have Cargo, and it works well, tying package updates to the language version has quite a bit of downside, and very little upside. With a good package management system, a batteries-included standard library could just be a set of packages where you are guaranteed that a version of each backward-compatible to the one provided at language r…
It's true that that's possible. Gotta have those libraries actually exist first, though :) We'll see if we don't end up with something like this.
Re: Announcing Rust 1.0 Alpha
#76Earlier quoted context omitted.
I think Python and Go are two examples where the standard library has very much proven invaluable. Without it, it's difficult to be confident in the portability of components, and it quite frankly makes the language less attractive for use. Like the other poster mentioned, I'm happy for the RUST folks to take a "wait-and-see" approach, but at some point, I believe "blessed" components are going to be expected and str…
> I think Python and Go are two examples where the standard library has very much proven invaluable. C#. The amount of time I've wasted in Java programming teams while arguing over things like which of three quirky XML parsing implmentations[1] was the One To Use while the .net team powered off and built useful functionality... [1] This was a few years ago, obviously.
So you prefer not having a choice over having a choice because choice will lead to discussions to pick the best solution.
Quite an odd view from a software engineer.
I like having as much choice as possible.
Re: Announcing Rust 1.0 Alpha
#77Re: Announcing Rust 1.0 Alpha
#78Wow. Anyone remembers Rust pre-0.1? When it had typestate, ML syntax, garbage collection, etc.? So nice to see how the language slowly evolved and was molded to fit as best as possible the problem they were trying to solve.
It's been a fascinating metamorphosis, undeniably. I'm going to attempt to turn it into an interesting talk for the tentative Rust conference that may be happening this year. :)
Re: Announcing Rust 1.0 Alpha
#79The one thing that would put rust over the top right now is something along the lines of gofmt - something simple, with zero configuration, that can be run on commit or even save.
gofmt is a huge win for Go. Bye bye bikeshedding. I'd love to see that for Rust too.
Re: Announcing Rust 1.0 Alpha
#80Coincidentally, I used Rust for a little board game solver this week and have been delighted by its performance and typechecker feedback! My Scala v1 was was very concise but took ~3 seconds to simulate a whole game. The naive Rust rewrite did it in 0.7 seconds and my current version churns them out at 0.015s each!! http://github.com/iamdanfox/qwirkler if you're curious.. This language is really fun!
Performance is an area where Rust still has a lot of low-hanging fruit to pick, so I'm happy to hear that you managed to make your version fast. Did you have to make any design compromises to that end? We're very interested in optimizing the typical use cases.