Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rust 1.5

blog.rust-lang.org

Post reply on HN
Print view View original

61–70 of 159 posts

Re: Rust 1.5

#61

Post by Argorak »

steveklabnik wrote: post #56
jeffdavis wrote: post #53

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 major movement on the ? syntax last night, actually.

Huh, does that reflect in RFCS or something somewhere?

I'm quite pleased by the current solution and am not such a big fan of "?".

Re: Rust 1.5

#62

Post by steveklabnik »

jeffdavis wrote: post #60
steveklabnik wrote: post #56

Earlier quoted context omitted.

There was major movement on the ? syntax last night, actually.

Great to hear! Thank you.

No problem. To be more specific, https://github.com/rust-lang/rfcs/pull/243#issuecomment-1633... and https://github.com/rust-lang/rfcs/pull/243#issuecomment-1633...

TL;DR: we're still adjusting process a bit, but the idea is that this is "good enough" to actually land, behind a feature gate, to start gaining experience. We still reserve the right to tweak it before it goes stable, but it's better to get it into people's hands, rather than continue to debate the last few minor points.

Re: Rust 1.5

#63

Post by sudeepj »

steveklabnik wrote: post #47
moonchrome wrote: post #33

Earlier quoted context omitted.

Well even a guesstimate would be nice :) I've been following Rust from sidelines before 1.0 and from my perspective there are advantages but I can also see a lot of pain in porting stuff and moving over and I right now the benefits don't outweigh the risk and cost for me - but having a fast build system (which implies incremental recompilation) along with a default package manager (which it already has) would be enou…

There's two components to this. I just asked the relevant people, they said "Six months is a safe guess, we hope sooner, we have ambitious plans, we'll see." However, there's also something mentioned in this announcement: cargo-check. In terms of the "I'm building a project and I don't want my builds to be slow," I think that cargo-check might even be more important. cargo-check relies on an important insight: many t…

Is this something which the editor plugins can make use of? (as a quick lint/feedback about the code). My guess is that the plugins actually use naked rustc call rather than cargo build.

Re: Rust 1.5

#64

Post by steveklabnik »

sudeepj wrote: post #63
steveklabnik wrote: post #47

Earlier quoted context omitted.

There's two components to this. I just asked the relevant people, they said "Six months is a safe guess, we hope sooner, we have ambitious plans, we'll see." However, there's also something mentioned in this announcement: cargo-check. In terms of the "I'm building a project and I don't want my builds to be slow," I think that cargo-check might even be more important. cargo-check relies on an important insight: many t…

Is this something which the editor plugins can make use of? (as a quick lint/feedback about the code). My guess is that the plugins actually use naked rustc call rather than cargo build.

Currently, it basically runs `rust -Zverbose -Zno-trans`, so yes. If it gets more advanced, we'll see.

Re: Rust 1.5

#65

Post by yokohummer7 »

mbrubeck wrote: post #32
andyl wrote: post #23

Browsing the names of contributors, I was surprised at the lack of gender diversity. Four or five female contributors at the very most. Rates of female participation below 5% - wow. Why is Rust lang so anti-female?

Sadly, this isn't even unusual. Open source developers as a whole are 90% male or more; some older surveys found the number higher than 98%. http://readwrite.com/2013/12/11/open-source-diversity As a long-time member of the Rust community I am seeing this changing over time, but much more slowly than I'd like. Rust is a very friendly community; we have an actively-enforced code of conduct (which has been in place sin…

I think this is just a reflection of the proportion of the female contributors in overall open source communities. There's really no reason for the Rust project to do anything "anti-female". Actually I think it is a bit too concerned with diversity.

Then the problem now becomes why there aren't that many female contributors out there. This is just a theory, but I think it is because males' nature make them do free labor to obtain fame. I admit this is purely my experience, but females are more likely to refrain from such labor that does not pay off.

Re: Rust 1.5

#66

Post by sanxiyn »

steveklabnik wrote: post #57
zaczac wrote: post #52

Is this coincident with Go 1.5 release?

No. We release every six weeks, period. Any resemblance to other releases, living or dead, is purely coincidental.

FYI, Go releases roughly every six months.

From http://blog.golang.org/go12, "This new release comes nearly seven months after the release of Go 1.1 in May. We anticipate a comparable interval between future major releases." Go 1.3 and 1.4 took six months, 1.5 eight months.

Re: Rust 1.5

#67

Post by lambda »

Drdrdrq wrote: post #54
lambda wrote: post #29

Earlier quoted context omitted.

What benefit would Docker images have over the existing upstream distribution or distro packaging? The Rust compiler doesn't have any particularly complicated dependencies, either installing the binaries directly from rust-lang.org or installing packages from your distro (if your distro has packages yet) should work fine. Container images are great for daemons with possibly complicated dependency sets that might have…

One benefit: one could install latest version of Rust on any distribution. Debian stable for instance usually lags behind (with good reason, but still...). I imagine it is mostly useful for checking out Rust though, not for normal use.

The installer from https://www.rust-lang.org works fine on Debian stable. Right now, you can just use the upstream rustup.sh script for platforms that don't yet have it packaged (like Debian stable), or install from your distro for those that do (or use rustup.sh on those as well if you like).

What I'm not seeing is the value of a Docker image. Rust doesn't have much in the way of runtime dependencies, which is where the value of a container generally comes in. I don't know of a platform where Docker image would work but rustup.sh would not.

Re: Rust 1.5

#68

Post by jeffdavis »

Argorak wrote: post #61
steveklabnik wrote: post #56

Earlier quoted context omitted.

There was major movement on the ? syntax last night, actually.

Huh, does that reflect in RFCS or something somewhere? I'm quite pleased by the current solution and am not such a big fan of "?".

I'm curious what you do. Do you use try!() extensively, and fine it just fine? Or do you use something else, like .unwrap()?

Re: Rust 1.5

#70

Post by Argorak »

jeffdavis wrote: post #68
Argorak wrote: post #61

Earlier quoted context omitted.

Huh, does that reflect in RFCS or something somewhere? I'm quite pleased by the current solution and am not such a big fan of "?".

I'm curious what you do. Do you use try!() extensively, and fine it just fine? Or do you use something else, like .unwrap()?

Yep, I just use try!(), with the appropriate From implementations.
Post reply on HN