101–110 of 159 posts
Earlier quoted context omitted.
I haven't written a lot of Rust, but what manual memory management are you referring to? As far as I can tell, the whole point of the language is that you don't have to worry about that if you listen to the compiler.
You have to think about it. You don't have to worry about it.
Earlier quoted context omitted.
I would certainly welcome changing master/slave to leader/follower. It's no less clear, and it doesn't associate my software with something I'm deeply against. People might have different reactions to this thing so what's a stupid change to you might be a crucial change to someone else. (I agree that changing man is a little silly as it's obviously short for manual)
I don't know, to me master/slave embodies teh relationship of the devices better than leader/follower, and also has less alternate meanings when viewed as a verb to confuse what is going on. Is the leader "out front"? Is the leader "first"? Is the follower doing the same thing, but delayed in some manner (which doesn't fit standby situations very well). A master controls. A slave is controlled. Additionally, I think…
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
Just a small remark. You might want to note in your readme why you'd want to use a fault-injection library. I wasn't familiar with the concept, and had to google why you'd want to do that (for testing unexpected errors and the application's handling of those errors).
Earlier quoted context omitted.
I don't see where anyone has proposed we "ban" any words at all. What I see are people who suggest that we use a different set of words, that accomplish the same ends as "master/slave," except with words that aren't associated with slavery. > "Masters and slaves have always existed in human history and will probably always exist" I don't understand this argument. I'm not saying your statement is wrong, but I fail to…
I don't accept that we can't use words that accurately describe a concept merely because some people find that concept unpleasant.
https://github.com/Homebrew/homebrew/blob/master/Library/For...
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 "?".
Earlier quoted context omitted.
I haven't written a lot of Rust, but what manual memory management are you referring to? As far as I can tell, the whole point of the language is that you don't have to worry about that if you listen to the compiler.
It's sort of the opposite, it's that the compiler won't permit you to neglect any aspect of memory management until it deems your work passable. You think about memory management even more than you would in most languages. The result is you get some guarantees about correctness.
Earlier quoted context omitted.
Don't you have anything better to do than gender-troll? Like write some code, maybe? For god's sake, Rust goes out of its way to be modern and gender-inclusive. They have a god damn code of conduct, explicitly encourage participation from everyone, and actively seek contributors of all types. What the else should they fucking do? Posts like yours just demonstrate that you can never win by giving into SJW demands. No…
"Rust goes out of its way to be modern and gender-inclusive." And yet - epic fail. What is the reason?
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.
$ multirust update
$ multirust show-default
multirust: default toolchain: stable
multirust: default location: (...)
rustc 1.5.0 (3d7cd77e4 2015-12-04)
cargo 0.6.0-nightly (e1ed995 2015-10-22)
$ multirust list-toolchains
beta
nightly
stable
$ du -hs ~/.multirust/
996M /home/e12e/.multirust/