We'll see what we can do in the future.

Set owner to @gbracha.
Added Accepted label.

This comment was originally written by @seaneagan

This is a duplicate of issue #1616. The proposal there:

https://docs.google.com/document/d/1Y-ec5lID7P0lf0nhNtgwAdGagnDqQN0KDeEOOrBFMik/edit

suggests to actually make methods desugar to Function-typed getters, so that it is transparent when using mirrors. Otherwise people will try to invoke a method using:

objectMirror.invoke(#m, [...], {...});

and it won't work in the case that m is implemented as a Function-typed getter, unless ObjectMirror#invoke is made to support this.

Fortunately, ObjectMirror#getField already does the right thing by closurizing methods.

This comment was originally written by @seaneagan

I filed issue #15138 for making this work with mirrors as well.

It's worth noting that it works at runtime.

That is:
  x.foo()
works whether x has a method named foo or a getter named foo that returns a function.

That means that this is the static type system getting in the way of something that the writer knows will work at runtime - something that Dart tries to avoid in general.

With the Dart 2 type system, this is definitely not viable.