<jaapz> Should I try to get into C before learning some more Rust?
<jaapz> Wouldn't i "get" rust better when I know which problems it tries to solve from a C perspective?
<kimundi> Would you start learning skateboarding without protective gear to know how painful it is when you fall?
From Reddit - Dive into anything by sigma914:
Rust has ruined C++ for me, Haskell has ruined Java/C# etc, and Lisp has ruined python/perl/ruby... I end up sitting there going "The compiler should be telling me this is safe!" or "God damnit I need a macro!" all day...
Thanks for the quotes again clever people!
<bluss> I've tried using unchecked indexing in non-trivial code now a couple of times. It never makes a big difference <bluss> Profiling shows like 1-2% improvement if that <bluss> so it's the tightest loops you should worry about, not much more
Because I want to grab that qotw pulpit to spread my dogma.
I don't know if that belongs here though.
<blue_deref> well, the thing is, you either understand it, or it /doesn't/ work
<blue_deref> so, yes, it always works the way you think it does
<blue_deref> The borrow checker will learn you much
I need a personal Gankro to cheer me up while I wait for rustc to compile.
Don't we all need our personal Gankro every now and then?
Sorry, but the Rust standard library doesn't provide crystal balls.
-- birkenfeld on rust-lang users
15:56 < tswett> Man. If I ever use Rust in an environment where a heap *is*
available, it's going to feel so luxurious.
I feel like some of these are not necessarily positive... i mean steves quote is about how much Rust sucks without the std-lib, and @llogiq's is about how the community cant read minds, and the one before that is about how dreadful Rustc is to compile.... not terrible quotes, but probably not what we want to put out in the public....?
Yes it is fun to jab about some of the pain points of Rust, but maybe not as the 'quote of the week'
I personally think it's refreshing to be part of a community that isn't afraid to highlight areas that can be improved.
Just you wait until the mind_reading
RFC is implemented...
Im fine with people commenting on what is bad about Rust, but is something slanderous of people or the language what we want as the weekly quote?
<Quxxy> Rust code takes so long to write that adding bugs would be too much effort, not to mention how slow the compiler is. It's easier to just write it correctly the first time.
The language? Heck yes. The people? Heck no!
unsafe
is as viral and pernicious as pop music, though obviously not as dangerous.
Talking to wycats about extending std::time:
<wycats> I just feel like in this case
<wycats> people think "just do a reasonable thing"
<wycats> but the results are basically violations of physics
ah I love this, when the bounds check has a purpose for the algorithm.
@bluss, in an itertools PR.