| 04:24 | <Mathieu Hofman> | I find it rather hard to justify that [value] if success and [undefined, reason] if throw. That way anyone that want to handle the unexpected case can use the arity of the returned tuple? Or if we absolutely want to put the error first, use a hole in the array instead of a reason. |
| 04:28 | <rkirsling> | this was an interesting read, and for like three extra reasons too: TIL that LJ lived on in a new form, TIL that "straitened" means "narrowed" (feel like this would be unintelligible when spoken 😅), and boy do I ever feel attacked by the "never identify with your virtue [of agreeableness]" part 🙈 |
| 06:08 | <ljharb> | we should never, ever, ever have a new API that produces holes |
| 06:34 | <rkirsling> | new normative convention: "topological homogeneity" |
| 07:17 | <Jesse> | as responsible language designers and maintainers, it's entirely appropriate to reflect on the nature of holes and come to a good conclusion about what to do. So I'm just gonna drop this here: https://plato.stanford.edu/entries/holes/ |
| 07:20 | <Rob Palmer> | That article is gold. |
| 07:20 | <ljharb> | this article reads like there's a dozen SCP reports between the lines, i love it |
| 07:23 | <ljharb> | also it reminds me of the infocom game where you can pick up a hole, have it in your inventory, and drop it on an arbitrary surface. |
| 07:25 | <Jesse> | I seem to recall a Loony Toons character that also had a hole? (Was it Bugs Bunny?) |
| 07:27 | <Rob Palmer> | That's one for the positions repo >TC39 regrets the _horror vacui_ of Arrays |
| 07:28 | <ljharb> | https://www.youtube.com/watch?v=XaakNHzFoXE&t=97s |
| 07:32 | <rkirsling> | I unironically love this article 😂 also:
hell yeah, I was just thinking about mr. modal realism yesterday |