Jon Pretty

@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? :-)

@viktorklang @xeno_by i.e. it could be as simple as writing `val foo: Foo = alloc`, (provided Foo has a zero-arity constructor).

@propensive @xeno_by I'd be fine with not having inference for it, it'd just be cleaner.