Live data from Hacker News

Rust 1.5

blog.rust-lang.org

111–120 of 159 posts

Re: Rust 1.5

#111
post #2

I have a small question : I have installed 1.4 through rustup.sh. What is the clean way to upgrade to 1.5 ? I don't think there is some kind of 'rustup.sh upgrade' Delete 1.4 & reinstall ? Or downloading rustup 1.5 will apply a clean install on the existing one ?

Run rustup.sh again, and it will Just Work. (If not, that's a bug.) If you want to have multiple versions installed at the same time, https://github.com/brson/multirust is super cool. Generally speaking, installation is something we're working on: working with Linux package maintainers, rolling rustup and multirust together and making them work well cross-platform, etc.

rustup.sh is really freaking awesome. I was shocked at how insane it is to set up Go when I peeped at my friend installing it.

Never heard of programming but you still want to compile a project?

Step 1: run rustup.sh (curl -sSf https://static.rust-lang.org/rustup.sh | sh)

Step 2: clone the repo of the project or your regional equivalent

Step 3: cargo build --release (or now with the new cargo install feature, cargo install)

Step 4: Enjoy

Re: Rust 1.5

#112
post #105

Homebrew's Rust receipt is still at 1.4 :( https://github.com/Homebrew/homebrew/blob/master/Library/For...

This doesn't look like 1.4 but _1.0.0-beta.4_, so much older.

Re: Rust 1.5

#113

I know this seems like a trivial issue, but I've been bothered by the try!() macro for a while. I keep hoping then will adopt the "?" postfix operator to mean the same thing, because it seems to increase readability a lot. I'm open to other ideas too, but that seemed like the simplest way to get the error handling out of the way. Ordinarily I try hard not to complain about syntax, but this seems to cause people to us…

There was just a burst of conversation on this and I think it will be accepted under a feature gate while they work some Type stuff out

Re: Rust 1.5

#114

Earlier quoted context omitted.

Yeah the master/slave thing pisses me off. They are words in the dictionary used to describe something and that is all.

Except that people's experience of words doesn't come from the dictionary. Words aren't experienced in a vacuum, people assign different meanings to words based on their own experiences. To some of us, "master/slave" is just a phrase to describe an architecture. To others of us, it has historical connotations that makes it inappropriate.

Okay but that doesn't mean the word stops existing. My point is that master and slave are general terms, not specific to one group of people. This is a slippery slope to go down.

Re: Rust 1.5

#116
post #44
post #4

How are compile times now? The one barrier I had to using Rust for anything large was the awful compile times. Very happy to see the tooling improvements, though. Great work!

How long is "long"? What sort of time would we be talking about for 100KLOC projects?

I don't know about 100K, but for my 5667 line project, a recent nightly build takes 8 seconds to build on my 2012 macbook pro (4 core 2.3G i7). That is with up-to-date external crates that aren't being rebuilt.

Typecheck happens early, with borrow-checking following soon after, so you get feedback on errors fast, and thus only end up waiting when the compiler is happy with your code. Still, it may be an issue for people who like to do TDD or need to do a lot of run-time verification.

For a big project you'd probably need to split it up into multiple crates to "emulate" incremental compilation, at least until it is supported by the build system.

Re: Rust 1.5

#117
post #105

Homebrew's Rust receipt is still at 1.4 :( https://github.com/Homebrew/homebrew/blob/master/Library/For...

This doesn't look like 1.4 but _1.0.0-beta.4_, so much older.

I've just updated the link.

It is 1.4 as I've brewed rust few minutes ago.

And you get the point, don't need to picky on the specifics.

Re: Rust 1.5

#118

Earlier quoted context omitted.

You have to think about it. You don't have to worry about it.

This sounds like Rust propaganda! It's too slick...

it sounds slick, but for the first few hours you'll think that hell is a nicer place than here because the borrow checker won't be there. it takes a while for it to become slick again and only then you really start to appreciate the language. theory vs practive and all that.

Re: Rust 1.5

#119
post #46

Earlier quoted context omitted.

I definitely know more women involved in Rust than I did a year ago [EDIT: in percentage terms, as well as absolute numbers] , but this might just reflect my own awareness rather than any greater trend. I don't have any non-anecdotal evidence. Actual surveys of Rust developers/users would be useful. Also, most of the people I know in the Rust community now are now "users" of the language, rather than people working o…

Oh, I agree there are more women involved, but I attribute that to greater popularity of Rust. What I don't see is change in relative number, not absolute number.

curious: do you see change in other OSS communities?

Re: Rust 1.5

#120

I've been excited to try Rust for some time now, but I've been holding off, only because I'm primarily developing web applications and I've heard from a few people that Rust is better suited for other tasks (based on the built-ins, packages, etc.?), despite there being at least a few frameworks out there. What are your thoughts on this? Have things changed? Is the assumption just dead wrong, and Rust is in fact treme…

I've been toying with a web app[1][2] using hyper[3] as for http connections and ws[4] for web socket connections. This was my first project using anything lower level than Javascript. I had a fairly good experience, my problems stemmed more from not knowing the least bit about memory management rather than lack of libraries. In fact the libraries that are already there tend to be very well documented, with lots of examples and explanations.

1: http://theremins.club

2: https://github.com/runarberg/theremins

3: https://crates.io/crates/hyper

4: https://crates.io/crates/ws

Post reply on HN