TIL, thanks
TIL, thanks
Moths have fur?
C’mon — you’re @programming.dev. You’re supposed to know why this is bad.
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.
Nix installs packages independently of what’s been installed, so you’ll get the exact same result if you skip 0 updates or 500.
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.
A MONAD IS A MONOID IN THE CATEGORY OF ENDOFUNCTORS
tips arch (btw)
DuckDuckGone
impl<'a, T: Child> ChildRef<'a, T> {
fn orphanize<T: Child>(r: Self) -> Orphan<T>;
}
Argument parsing; turning Rc
foo
=
bar
into Reconfigure(|c| c.foo = "bar")
.
-- |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 ()
Haskell, my favorite pythonlike!
I present to you quality variable names. (and a Mount Rustmore)
(Reconfigure(f), 'c') => {
let mut p: Vec<&str> = vec![];
loop {
match args.next() {
Some(k) => {
if k == "=" {
match args.next() {
None => q("need value for Rc"),
Some(v) => u(
f,
|f| Box::new(
|c| {
f(c);
c.set(p.iter().copied(), v);
for e in p {
unsafe {
Box::<str>::from_raw(
std::mem::transmute(e)
);
}
}
}
)
)
};
break
} else {
p.push(Box::leak(k.into()));
}
}
None => error("need path element or = for Rc"),
}
}
},
deleted by creator
Press XN, I dare you.
Metric = a measurement, not the metric system.