![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8f2046ae-5d2e-495f-b467-f7b14ccb4152.png)
What the fuck, US?
Also, it appears said prosecutors are here and downvoting this.
What the fuck, US?
Also, it appears said prosecutors are here and downvoting this.
Yep, parentheses force {}
to be interpreted as an expression rather than a block — same reason why IIFEs have !function
instead of just function
.
The inspector REPL evaluates as a statement-with-value (like eval
), so the {}
at the beginning is considered an empty block, not an object. This leaves +[]
, which is 0. I don’t know what would make Node differ, however.
Edit: Tested it myself. It seems Node prefers evaluating this as an expression when it can, but explicitly using eval
gives the inspector behavior:
I can’t tell if this is Poe’s law or not.
Flaked NixOS unstable
I’m blind, sorry
No NixOS?
nix run nixpkgs#firefox
Yes, as well as automatically hiding new comments.
checks instance oh that makes sense nvm
Oh, that makes more sense! Thanks
What is the top graph? It seems to be some combined thing, but I can’t figure out what.
A MONAD IS A MONOID IN THE CATEGORY OF ENDOFUNCTORS
Sadly you can’t build a singleton. AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactoryBuilder$Companion
?
Happy non-🍰 day!
Nix installs packages independently of what’s been installed, so you’ll get the exact same result if you skip 0 updates or 500.