Interesting project but this write-up has a bizarre focus on number of lines of code, which doesn’t appear to differ substantially between the two approaches.
Go’s error handling is fine. I don’t hate it, in spite of it being verbose. I’d love to see something like Result, Option, pattern matching, and something like the ? operator from Rust, but the official proposals on the topic are never taken up.
In the end, it still has errors as values which is worth a lot. I’m fine with a few lines per check.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
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
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
Interesting project but this write-up has a bizarre focus on number of lines of code, which doesn’t appear to differ substantially between the two approaches.
Go’s error handling is fine. I don’t hate it, in spite of it being verbose. I’d love to see something like
Result,Option, pattern matching, and something like the?operator from Rust, but the official proposals on the topic are never taken up.In the end, it still has errors as values which is worth a lot. I’m fine with a few lines per check.