51–60 of 137 posts
Earlier quoted context omitted.
There's plenty of precedent. It's just rare for a reason. I'm not sure allowing slightly easier access to CSS syntax justifies it.
Out of curiosity, what's that reason?
This language may require whitespace around all operators, though. It's not clear to me.
fact(match) = 0 or 1 -> 1 n -> n * fact(n - 1) why not simply fact(0 or 1) -> 1 fact(n) -> n * fact(n - 1)
I think in Erlang the function identification is the name and the arity and this is as close I know of what you would like to have.
Earlier quoted context omitted.
I think it's unfortunate that this is currently the top comment on this post. Someone puts hundreds of commits of work into a nifty language with a nice feature set (including compile-to-js) and awesome integrations, and this is what they get on HN... I think this looks like a great project, we can never have too many programming languages to play around with.
>we can never have too many programming languages to play around with. Wait until we start having legacy code in all those languages. >we use 30 different compile-to-js languages used in our projects(that are no longer being developed) and you have to maintain it.
"Oh god, do we need another language that compiles to javascript?!" —Everyone, probably
fact(match) = 0 or 1 -> 1 n -> n * fact(n - 1) why not simply fact(0 or 1) -> 1 fact(n) -> n * fact(n - 1)
That said, I really like the inclusion of async and a DSL for documents. These two are things that benefit a lot from having language support.
Earlier quoted context omitted.
There's plenty of precedent. It's just rare for a reason. I'm not sure allowing slightly easier access to CSS syntax justifies it.
I'd love to hear why people prefer underscores over hyphens. I think I grew out of syntax fanboy-ism, but C and python __private__, _special_variable are everything but readable to me. They break the visual line too much. Even historically it was a weird symbol, originally a line break that made it into non-space separator in PL/1, then almost everywhere. Before that it was pure formatting, a typewriter glyph to be o…
Because I like subtraction.
The "fact(match)" is very strange. In Haskell you have "lambda-case" and in Ocaml you have "fun" as syntaxes to define lambdas that pattern-match on the argument. That said, I really like the inclusion of async and a DSL for documents. These two are things that benefit a lot from having language support.
f(x, y) =
match x:
{m, n} ->
match m:
n + y
else -> m + n + y
n -> n + y
f(match x, y) =
{match m, n} ->
n + y
else -> m + n + y
n -> n + y