Conversation

wat, are the precedences and associativies hard-coded?

Yes. An operator is right-associative if it ends with a colon, except for => and -> which are hardcoded to be right-associative.

omg

This is why `a +: b` is actually a call to `b.+:(a)` on collections ;)

what is

oh and this is another thing sorry but def ident(Args): Ret is wrong. but no language can have perfect syntax I suppose. 😔

I like it because it unifies function definitions and value definitions

mmm. I did notice that but the arrow of implication still makes more sense to me, as with in Rust's let fun: fn(Arg) -> Ret = |arg| arg.val;

5:41 AM · Sep 28, 2021Twitter Web App

val fun: Arg => Ret def fun(Arg): Ret when you don't have a function arrow (i.e. =>) then definitely I'd go with ->. but Scala has function arrow

Replying to

yeah, I like this. it makes sense in SML, OCaml, and Lean for similar reasons, for example in Lean 4 you have something like: def foo (arg1 : Arg1) (arg2 : Arg2) : Ret := .... Is sugar for: def foo : Arg1 -> Arg2 -> Ret = fun arg1 arg2 => ...

Replying to

That's still in curried languages though. Scala isn't curried