I guess, opening a PR without forking is possible, but hey that’s sort of incredibly bullshit idea
Rust dev, I enjoy reading and playing games, I also usually like to spend time with friends.
You can reach me on mastodon @sukhmel@mastodon.online or telegram @sukhmel@tg
I guess, opening a PR without forking is possible, but hey that’s sort of incredibly bullshit idea
Pretty much sums my experience with windows, something you want will either work fine, or be mysteriously broken beyond repair with no apparent reason. MacOS is like that sometimes, too. Linux is not perfect, but it usually allows for a fix to exist.
Not only them, and I’m not here to blame 😅
There’s no such thing as “zeroith” because it’s called “zeroth — being numbered zero in a series”
This works for building storeys, this would work equally well for tables. The only reason this is not used often is because the series are rarely zero-based in anything that doesn’t also want to equate index and offset.
You’re right that first may be read as “opposite of last”, that would add to the confusion, but that’s just natural language not being precise enough.
Edit: spelling
Edit2: also, if you extend that logic, when you’re presented with an ordinal number, you would need to first check all the options, sort them, and then apply the position you’re asked, that’s not really how people would expect ordinal number to be treated, not me, at the very least
Wow, Republicans are Marxists 🤔
Reminds me of how I found some safety measures to be in China some years back, basically those were signs saying “plz don’t fall to your death, if you do it’s your fault”
Well, there is cve-rs, just sayin’
If you want everyone to stop trying to shove Rust everywhere, just use smart pointers more. I may somehow get over Rust not replacing every other language if those languages will be safe
I think, the idea was along the lines of “because C++ was not memory-safe, and it has to stay compatible with how it was, there are still a lot of ways to not write memory-safely”
This makes sense, there are memory-safely features available but there are a lot of programmers that will never willingly use that features, because the olden ways are surely better
Other than that, I agree, when you’re paid to fix an unfixable problem you will probably claim something like that and advocate for your solution being the only one that solves this
That was about what I meant, but thanks for expressing this, sorry I was vague.
…but still edible. I usually alternate between eating kiwi whole and with a spoon ¯\_(ツ)_/¯
You were supposed to not eat those? Well, I figured, I’m not obligated to eat everything if I want less spicy, but I never thought that those are decorative
I first thought you were talking about waving to pedestrians to cross when you stop to let them go. Which (edit: stopping and waiting) is a correct and expected behaviour, afaik
Are we still talking about COBOL?
To be fair, I disagree with all the points author makes, except for performance which is important but may be less important than code clarity in different cases. I am surprised that exceptions perform that well, and I am surprised the author said that compared C++ exceptions to Rust results, but actually did the right thing and compared C++ exceptions with C++ expected first. I thought it was going to be one of those “let’s compare assembly to lisp”
Yeah, I shaped my words poorly. What I meant is that errors are sort of equivalent to exceptions, but errors are first class citizens of type system, and this is an improvement over exceptions being kind of independent of type
Have you ever worked at large old corporation? Wasting money is a bit of an underestimation on that scale.
Also, not all banks use COBOL, but the ones that don’t are usually much younger.
Besides, Ada would’ve been a better example, as it is used by telecoms and seems to be held in high regard, unlike COBOL. The only issue with Ada I heard of is that it’s on par with C++ in complexity which is far from being simple.
I’m just going to ask, without making assumptions. Have you managed to cut some time to read the article and find an answer?
you never know what code your function or library calls that can produce an exception
As far as I remember, there were several attempts at introducing exceptions into type system, and all have failed to a various degree. C++ abandoned the idea completely, Java has a half-assed exception signature where you can always throw an unexpected exception if it’s runtime exception, mist likely there were other cases, too.
So yeah, exception as part of explicit function signature is a vast improvement, I completely agree
I thought a lot of places are like that, that’s why we get all the fences and such 🤔