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

131–140 of 159 posts

Re: Rust 1.5

#131

Post by steveklabnik »

eoi wrote: post #129
e12e wrote: post #109

Earlier quoted context omitted.

Strongly recommend multirust. It can eat a bit of space if you end up with both stable, beta and nightly installed (but that can still be a good idea -- obviously lots of new projects will experiment with some new features). But multirust takes a lot of cues from other similar tools for sandboxing. I just did: $ multirust update $ multirust show-default multirust: default toolchain: stable multirust: default location…

Also worth noting is multirust-rs, a reimplementation of multirust in Rust, which notably adds Windows support. I haven't tried anything fancy with it yet but so far it just works. https://github.com/Diggsey/multirust-rs

The intention is to unify this, multirust, and rustup.sh. It will probably just be branded "rustup."

Re: Rust 1.5

#132

Post by aldanor »

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…

Agreed, if you work with I/O, all the try!(try!(try!())) start making your eyes bleed. The ? suggestion is quite brilliant, been waiting for progress on that for a long time

Re: Rust 1.5

#133

Post by rhodysurf »

untothebreach wrote: post #128
rhodysurf wrote: post #127

Earlier quoted context omitted.

By this thinking any word without context can cause outrage.

All I'm saying, is if you recognize that a word is potentially costing you contributors, why wouldn't you change it if there is another word that is just as good? I'm just trying to be practical, not trying to force PC-think down anyone's throat.

Right, but in this case master slave often describes the relationship between computer devices better than anything else. The slave device has no choice of what to do other than what a master device sends it. Leader and follower doest quite capture that as well in my mind.

Re: Rust 1.5

#134

Post by toqueteos »

eoi wrote: post #129
e12e wrote: post #109

Earlier quoted context omitted.

Strongly recommend multirust. It can eat a bit of space if you end up with both stable, beta and nightly installed (but that can still be a good idea -- obviously lots of new projects will experiment with some new features). But multirust takes a lot of cues from other similar tools for sandboxing. I just did: $ multirust update $ multirust show-default multirust: default toolchain: stable multirust: default location…

Also worth noting is multirust-rs, a reimplementation of multirust in Rust, which notably adds Windows support. I haven't tried anything fancy with it yet but so far it just works. https://github.com/Diggsey/multirust-rs

Thank you so much for posting this. I was expecting something like this to pop but never tried searching.

Re: Rust 1.5

#135

Post by untothebreach »

rhodysurf wrote: post #133
untothebreach wrote: post #128

Earlier quoted context omitted.

All I'm saying, is if you recognize that a word is potentially costing you contributors, why wouldn't you change it if there is another word that is just as good? I'm just trying to be practical, not trying to force PC-think down anyone's throat.

Right, but in this case master slave often describes the relationship between computer devices better than anything else. The slave device has no choice of what to do other than what a master device sends it. Leader and follower doest quite capture that as well in my mind.

> has no choice of what to do

Tell that to the MySQL cluster I inherited at my last job ;-).

In all seriousness, I have to disagree with you, in that I think leader/follower captures the relationship fine. But at this point, I think "whether the word captures the relationship" is very subjective.

Re: Rust 1.5

#136

Post by mwfunk »

kozukumi wrote: post #35
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?

I hope you are trolling. Would more women in tech be good? Of course! However there is some crazy SJW stuff going on at the moment in a lot of projects. People pushing for things like Master/Slave to be renamed to Leader/Follower. Wanting things like man (as in the man command on Linux) renamed to something non-gender-based. I mean fucking come on. I am all for a more inclusive environment but some things are just st…

All of those things sound like isolated incidents rather than actual trends. Just using the term "SJW" communicates that you're in a constant state of readiness to be outraged about that stuff. Just treat it like the occasional silly overreaching that it is and be done with it, otherwise it creates an environment where there's no room for "community culture" discussions, ever.

Any time a community increases in diversity, there's a chance for friction. Maybe it's from old-timers with poor social skills who don't realize they've been in a bubble. Maybe it's from new people with their own problems, trying to blame the old culture for their own difficulties fitting in. You know what it's not? A conspiracy or a trend. The only constructive, grown-up thing to do is to try to understand and have empathy for both groups, while pointedly not belonging to either one.

In my experience, any time there's a kerfluffle about someone wanting to rename man(1) or , it's a very small group or an individual getting outraged over something silly, and an equally small group getting outraged over the first group's outrage. It's pointless and meaningless to the vast majority of the group, who just want to move on with their lives and get something done.

If these things seem like they're more common now in open source than they were 10-20 years ago, (a) you'd be mistaken, and (b) if anything, that's just a sign of more people becoming involved, which is a good thing. Let 100 more people in, and chances are one of them will be a little crazy. That doesn't mean they all are, it just goes with the territory.

Re: Rust 1.5

#137

Post by jamwt »

pjc50 wrote: post #44
clessg wrote: 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?

You would definitely split that project up into multiple crates at the moment. 100KLOC would take an eternity to compile. My guess would be 15 to 45 minutes for a release build, depending on things like how much you were using generics.

Re: Rust 1.5

#138

Post by AnimalMuppet »

untothebreach wrote: post #104
rewqfdsa wrote: post #87

Earlier quoted context omitted.

I don't accept that we can't use words that accurately describe a concept merely because some people find that concept unpleasant.

Really? Slavery is "unpleasant?" Going to the dentist is "unpleasant." The enslavement of an entire race of people goes quite a ways beyond "unpleasant."

> The enslavement of an entire race of people goes quite a ways beyond "unpleasant."

Absolutely. But what we're talking about isn't racial. The last time I worked on a master/slave setup (I forget whether we used those terms), the "master" and "slave" were of the same race. In fact, the slave could become the master, and the master could become the slave.

You may tell me that we're talking about the words, and I suppose that's true. But the words are also used for same-race slavery, so the words are not inherently about a racially-charged situation either.

Re: Rust 1.5

#139

Post by kibwen »

wyldfire wrote: post #21

Congrats to the team! I recently wrote my first Rust [1] project. Great experience, IMO. I faced a lot of interesting challenges because my use case was a little outside of typical. But I tried to minimize 'unsafe' and I was still satisfied with the results so far. I know I've only just scratched the surface of the language and I'm looking forward to learning more. [1] https://github.com/androm3da/libfaultinj

This looks like a really cool utility! What other tools out there provide the same service, and how do they compare to this?

Re: Rust 1.5

#140

Post by kibwen »

Cshelton wrote: post #6

Congrats first of all! I love Rust and am using it more and more. I'm very excited for 'cargo watch'. These tools built into the package manager will be so helpful with peoples' first time Rust experience. I think I'm going to say it, Rust has my favorite package management system of any language I've used. Side Note: I'm also a fan of the 6 week release assembly line Rust has going on. I'm glad that it's staying con…

I was actually suggesting that the Rust devs delay the release until next week because all the release orchestrators are fully occupied with the bi-annual Mozilla workweek, but it seems that they've managed to pull it off without a hitch. :)
Post reply on HN