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 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.
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:
A MONAD IS A MONOID IN THE CATEGORY OF ENDOFUNCTORS
tips arch (btw)
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.
fia? fir? fib (part of fia)?
Still needs to be widely used. It took me about an hour to figure out that my encoding issues were because of Vim being in latin1, another to figure out how to change that, and a third to realize that screen also wasn’t in UTF-8 mode.
There isn’t an unnecessary level of capitalization; seems to be regular Java with Allman braces.
The Microsoft Store adds a lot of restrictions to their programs (example of Python’s problems).
It can run in regular JS; print()
just prints the page (ignoring the passed value).
Haskell’s crazy operation is intuitive though. Assuming you’re talking about >=
, it’s just a generalized flatMap
.
Simple; take a picture of yourself to hold a circular reference.