Programming

17362 readers

209 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Why I Prefer Exceptions to Error Values (cedardb.com)

submitted 1 month ago by AlexKochetkova@programming.dev to c/programming@programming.dev

45 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] lysdexic@programming.dev -2 points 1 month ago (1 children)

I mean, yeah, if your language does not support error values, do not use them.

Nonsense. If adopting info of the many libraries already available is not for you, it's trivial to roll your own result type.

Even if that was somehow unexplainably not an option, even the laziest of developers can write a function to return a std::tuple or a std::pair and use structured binding.

[–] marcos@lemmy.world 10 points 1 month ago (1 children)

The problem is not encoding the result.

The problem is that you need some support from the language to make it easy to deal with. Otherwise you'll get into go-style infinite if (err != null) handlers that will make your code unreadable.

[+] lysdexic@programming.dev -6 points 1 month ago (1 children)

The problem is that you need some support from the language to make it easy to deal with.

Nonsense.

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

[–] sukhmel@programming.dev 6 points 1 month ago (2 children)

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.

[–] lysdexic@programming.dev -2 points 1 month ago

I feel like this will have zero protection against

Zero protections against what? Against the programmer telling the program to do something it shouldn't? Not programming language does that. If you resort to this sort of convoluted reasoning, the same hypothetical programmer can also swallow all exceptions.

The main problem you're creating for yourself is that you've been given an open-ended problem but instead prefer to not look for solutions.