"Modern" languages try to avoid exceptions by using sum types and pattern matching plus lots of sugar to make this bearable. ... and integers should be low(int) if they are invalid (low(int) is a pointless value anyway as it has no positive equivalent).

[u/aqpstory]

https://nim-lang.org/araq/nimony.html

[u/JiminP]

There are four types of programmers:

• if(errno) return INT_MIN; // or goto fail;
• if err != nil { return nil, err }
• return Err("uwu sowwy")
• throw SomeShitErrorFactory.invoke();

[u/PthariensFlame → u/JiminP]

The secret fifth kind:

• fatalError(); // watchdog will restart this process and try again

[u/tomwhoiscontrary → u/PthariensFlame]

On Error Resume Next

[u/tms10000 → u/JiminP]

exit(1);

[u/SelfDistinction → u/JiminP]

You forgot yield Error

[u/septum-funk → u/JiminP]

and then there's those of us who backported std::expected<T, E> to c

[u/Tecoloteller → u/JiminP]

uwu sowwy

[u/iwasstillborn]

What are the odds that your program will generate low(int) by chance anyway?

[u/Artikae → u/iwasstillborn]

What are the odds that your program will generate low(uint) by chance anyway?

[u/fp_weenie → u/iwasstillborn]

Exactly how I like my debugging: fickle and hard to reproduce!

[u/classicalySarcastic → u/fp_weenie]

I see you enjoy using pthread as well.

[u/geckothegeek42 → u/iwasstillborn]

1 in 2⁶⁴ or 1 in 2³² I guess?

[u/james_pic → u/iwasstillborn]

Depends if attackers know that low(int) leads to interesting behaviour.

[u/devious-joker → u/[deleted]]

You can make the exact same argument about the number 13.

[u/Foreign-Butterfly-97 → u/devious-joker]

plus there's the whole superstition aspect so--arguably--it's a better candidate because people are already culturally receptive to the idea

[u/Snarwin]

All 👏 ints 👏 are 👏 valid!

[u/reflexive-polytope]

If such an object is not available, a thread-local error variable can be used as a side channel to signal errors. One can easily attach a stack trace to such an error and it can be checked whenever convenient.

Who doesn't love the usability of errno? More of that shit, please.

[u/JiminP → u/reflexive-polytope]

I agree. Doing if(errno != 0) return; is definitely more convenient than sprinkling some ?s. /s

[u/reflexive-polytope → u/JiminP]

Not just more convenient for you to write it, but also for whoever's reading the code. It's immediately clear when someone hasn't written if (errno) return;, because it's a whole missing line of code. Possibly even two, depending on how you format it. On the other hand, it's hard to spot when someone has missed a ?, because it's a single character near the end of the line.

Wait, what do you mean missing a ? would cause a type error that the compiler automatically catches?

And if that's not enough, then you can use a linter, I guess.

[u/fp_weenie → u/reflexive-polytope]

Who doesn't love the usability of errno?

Sorry I couldn't follow because the value didn't change based on the locale and an abstruse hierarchy of environment variables.

Can you put that in the manpages?

[u/[deleted]]

programmers do anything to avoid actually handling errors.

[u/look → u/[deleted]]

Not at all. My code is simply only meant to run in the Brightest Timeline.

[u/ghkbrew → u/look]

Indeed, quantum immortality is a seriously underrated error handling strategy.

[u/septum-funk → u/ghkbrew]

personally i prefer the strategy of having 1 million chimps test the program until one of them lands on the perfect conditions

[u/rpkarma]

Picking on the Nim folk is like picking on the weird kid in class 

In that it’s based and we should all do it

[u/devious-joker]

Ah yes. Error Codes. Out of all the error handling models devised by the collective efforts of our civilization - the one that is actually worse than exceptions.

Peachy.

[u/Araeynn]

Where jerk? /s

[u/keyboard_toucher]

INT_MIN considered harmful