3·
1 年前Connections
Puzzle #842
🟨🟨🟨🟨
🟦🟦🟦🟦
🟩🟩🟩🟩
🟪🟪🟪🟪
I found this one so hard to break in
mercator_rejection
- 0 Posts
- 17 Comments
Joined 3 年前
Cake day: 2023年6月14日
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Connections Puzzle #834 🟪🟪🟪🟪 🟦🟦🟦🟦 🟩🟩🟩🟩 🟨🟨🟨🟨
2·1 年前At work we literally just went through this yesterday, just with
folly::Expected. A new guy joined the team and wanted to propose we update how we handle errors.
Connections Puzzle #823 🟩🟦🟪🟨 🟦🟦🟦🟦 🟪🟪🟪🟪 🟩🟩🟩🟩 🟨🟨🟨🟨I got hit by the same rainbow herring
Connections Puzzle #813 🟩🟩🟩🟩 🟨🟨🟨🟨 🟦🟪🟦🟦 🟪🟦🟦🟦 🟦🟪🟦🟦 🟦🟦🟦🟦 🟪🟪🟪🟪I had no idea on blue or purple…I had to guess with ‘one away’
Connections Puzzle #807 🟨🟨🟨🟨 🟪🟦🟩🟩 🟪🟪🟪🟪 🟦🟩🟦🟦 🟦🟦🟦🟦 🟩🟩🟩🟩I had an awfully hard time with all the animals and how they might be there
Connections Puzzle #802 🟩🟩🟩🟩 🟪🟨🟨🟨 🟨🟨🟨🟨 🟪🟦🟦🟦 🟪🟦🟪🟦 🟦🟪🟪🟦I had so much trouble with this one. didn’t know some of the concepts and couldn’t make it work out
Connections Puzzle #800 🟪🟪🟪🟪 🟦🟦🟦🟦 🟨🟨🟨🟨 🟩🟩🟩🟩I got blue kind of by accident, really.
Connections Puzzle #797 🟪🟪🟪🟪 🟦🟦🟦🟦 🟨🟩🟩🟩 🟩🟩🟩🟩 🟨🟨🟨🟨I misclicked one on green, dang
Connections Puzzle #796 🟪🟪🟪🟪 🟩🟩🟩🟩 🟦🟦🟦🟦 🟨🟨🟨🟨
I got
🟪🟪🟪🟪 🟨🟨🟨🟨 🟦🟦🟦🟦 🟩🟩🟩🟩Today
So uh… How did this turn out?
Honestly, looks ghastly. In the pursuit of being generic, they made something simple and straightforward into something unusable.
1·3 年前I have used DukTape in the past, it is an ECMAScript (javascript) implementation. The API is amazing, very consistent parameter and naming schemes, uses a stack based approach (feels like a better version of how lua goes about things). It is designed to be embedded. Documentation for the API is some of the best you will see, lots of good examples. It even has a debugger that you can hook into.
The main problem with
std:: expectedis lack of language support. In theory, it works well as an alternative to exceptions, with nice self contained monadic statements. In practice, it is actually much worse than what the article suggests.main issues -
-
as I said, no language level support. You eventually end up with messy code somewhere because the library code can’t simplify things enough. You end up with if checks strew about that really oaught to be a language paradigm.
-
there is not a lot of code making use of it, so at the boundaries of your code you have to make adaptations to and from
std:: expectedfrom whatever some library chose to use. -
adapting your existing codebase is basically impossible. Perhaps if you are starting a new project you can do it, but it is different enough that all your existing code must be updated to accommodate the new paradigm and it’s just an awful experience doing the work and being in a mix of error handling.
-
4·3 年前These examples didn’t actually clear anything up for me 🙃
Connections Puzzle #858 🟩🟩🟩🟩 🟨🟨🟨🟨 🟪🟪🟪🟪 🟦🟦🟦🟦I was only able to find blue and purple after put in green and yellow