Open akx opened 11 years ago
syntactically conflitcts with &&, no ?
&& isn't unary though, so maybe something could be done to allow it in a prefix/standalone context. Either way making this change would break some programs that currently rely on space/newline elision before && (like what happens in the "currently compiled" result there).
&^
, &^^
etc. would also be a (weird?) alternate syntax if &&
, &&&
, etc. aren't a Good Idea.
Well, & isn't unary either (and shows some problems, sometimes).
currently compiles to
though it might be a nice feature to have N+1 ampersands refer to upper
&
scopes, ieEDIT: (and &&&, &&&& etc. of course)