Yep, parentheses force {}
to be interpreted as an expression rather than a block — same reason why IIFEs have !function
instead of just function
.
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:
nix run nixpkgs#firefox
Yes, as well as automatically hiding new comments.
checks instance oh that makes sense nvm
A MONAD IS A MONOID IN THE CATEGORY OF ENDOFUNCTORS
As is the ____ in F_F_
Installed NixOS but don’t like NixOS? Try nix-env -iA estrogen
.
LiNuX uSeR iNsTaLlInG A BrOwSeR haha
yeah uh…
sudo apt install firefox
sudo xbps-install firefox
sudo pacman -Syu firefox
nix-env -iA firefox
impl<'a, T: Child> ChildRef<'a, T> {
fn orphanize<T: Child>(r: Self) -> Orphan<T>;
}
-- |Removes the given object from its current parent, if any, and then adds it as a child of the other given object.
kidnap :: ChildBearing c p
=> p -- ^The kidnapper.
-> c -- ^The child to kidnap.
IO ()
Is that TV just a CentOS box running VLC‽
I’m glad Voyager puts baby icons on new accounts; it usually resembles how they look in real life.
I calmly remove my USB labeled “oh shit” from my pocket, insert it, and reboot.
That’s why I put Linux on my house.
Nix has flakes;
nix run
can contain pretty much all of the needed dependencies. If that’s not enough, you can set up an entire container as a module.