Jon Pretty

Scala's `new` syntax is an anomaly. I'd rather say `new[Foo](x, y, z)`, or just `new(x, y, z)` if `Foo` is the expected type.

@propensive TBH I am more and more against `new` at all, since it precludes instance reuse. (i.e. only makes sense for mutability)

@viktorklang Particular thing that gets me is the precedence of dot vs space in, e.g., `new Foo().bar`.

@propensive Oh yes! I still, out of habit and expecation, always surround it with its paren(t)s. `(new Foo).bar`

@viktorklang Yeah, that's nice and unambiguous. Just seems a bit clunky...

@propensive Absolutely. Thinking of which, you could most probably create an `alloc` macro to allow for: `val foo = alloc[Foo](bar, baz)`

@viktorklang Yes, that's what I wanted to do. @xeno_by said I couldn't access the expected type, so `alloc(bar, baz): Foo` would never work.

@propensive @xeno_by Could you elaborate on that? :-)