lad

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 feel like this will have zero protection against

if (result.isSuccess()) {
    handle_error(result.error);
} else {
    do_something(result.value);
}

Besides, this is exactly what the comment said about having to constantly check for return values at call site. I think this may be mitigated by some clever macro-magic, but that will become a mess fast.

I don’t know the answer to your question, but I think that what is needed is just a bit of syntactic sugar, e.g. Rust has ? for returning compatible errors without looking into them. That seems to be powered by Try trait, that may be a monad, but I am not fluent enough to check if it formally is.

It’s used because the ones who use it have enough money to pay for any problems that may arise from it’s use, and known problems are deemed better than unknown ones.

It is a viable model when you have enough money and resources, but a conservative one

it’s one of the most popular languages used for C/C++ build scripting

Unfortunately 😅

That way we’ll just find maintainers went near extinct over time, just like COBOL developers that are as rare as they are expensive. Only Linux kernel isn’t a bank, and maybe will not have as much money to pay to rare developers capable of maintaining C codebase

It’s the number of the signal sent, 9 is for SIGKILL. You can send various signals with kill, and depending on how application was made it may react on all signals with dying, or meaningfully process most of them. Afaik, SIGKILL can’t be processed by the app, and it always means just that: “die already”.

Checked in Wikipedia, that’s about right but there are more details I left out, mostly because didn’t know about them, too: POSIX signals

The hard part is “that add value”. Not only it’s hard to measure, but highly depends on scope of what is done

Nah, this could’ve been possible with some clever fuckery in defining those emojis’ unicode content, like with flags that are not a single point but three independent ones, allowing you to do this:

"🇧🇬".reverse() == "🇬🇧"
"🇬🇪".reverse() == "🇪🇬"

Yet we live in a world where

Afaik, comes from Latin that had no “U” and “V” was both vowel and consonant until some point in time.

So, you’ve got no issues with “g” being sometimes kinda “h”, “j” being same kind of “h” always, “h” not being a sound a all, “d” sounding like “th”, and “z” sounding like “th” but another “th”, not the one for “d”. Oh, and “c” sounding either like “k” or like the latter “th”

I know some people that claim that everyone should use Latin alphabet, because you then know what things sound like, but that is the most bullshit take I ever heard. I guess that knowing how to write letters helps, but it looks like every other language pronounces those letters different, and English makes extra effort to pronounce different even the same things

Cosmic balance, sort of 😅

I forgot that last time was in 2023, although the previous one was in 2016. SO had a lot of moderation drama and point-grinders that (imo) led to community becoming more toxic, to the point where it’s not too pleasant for me to participate in.

To be fair, they still have some good answers, and sometimes they can provide a useful answer, but edge-case rare obscure problems that seemed to be the very reason for SO are rarely answered now, as I see it

I see now, that you were misunderstood in some parts.

even if I got reported a really weird bug related to UB, I should (I am not experienced enough to make a claim) be able to know it’s UB since the game’s gonna crash when I try to recreate the bug in Debug.

This may be problematic for several reasons: it may be hard to reproduce, the more complicated the state, the harder; bug may rely on some race condition that may be much rarer in Debug because of speed difference; UB is notorious for causing things that should (seemingly) never happen, like returning from infinite loops, proving false statements true, and such, so it may be hard to understand what at all happened and why.

Regarding optimisations, it might still be better to try to profile the code (I will be honest, I don’t do that until the moment when I can’t go further without optimisation, and I haven’t reached that with Rust) and see what are the real hot spots that require optimisations. I hope that someday you will be able to upgrade your machine, and hope that your game will be a good example of something that really runs anywhere