Comment #1 on issue 880 by tu...(a)tudorgirba.com: Improving VerveineJ stub
invocations/methods
http://code.google.com/p/moose-technology/issues/detail?id=880
Actually, this observation applies not just for invocations to stub
methods, but for any kind of invocations.
Let's take the invocation example:
aMethod(a, b()), where a and b() are of types A and B, respectively
Right now, even if we know the method, we get as a signature aMethod(A, B).
This information is essentially not useful, because we already have the
definition of the method and its parameters.
So, even in this case, we would still benefit from having aMethod(a, b())
as a signature because it provides extra information.