Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Varargs methods are problematic #1

Open
GoogleCodeExporter opened this issue Jul 3, 2015 · 0 comments
Open

Varargs methods are problematic #1

GoogleCodeExporter opened this issue Jul 3, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Varargs methods are problematic: we're taking foo(arg1, arg2, vargs) and
turning it into RT.invoke(recv, name, vargs) which necessitates
re-resolving the matching vararg method at runtime (currently with no
static type information).

Maybe all of this can be circumvented by not invoking methods reflectively
when they successfully resolve.

We need to avoid passing array as sole final argument to RT.invoke and
RT.invokeStatic, can happen when passing an argument in an untransformed
method and for literals:
  * main(String[] args) { foo(args); }
  * foo(new String[] { ... })

Original issue reported on code.google.com by [email protected] on 3 May 2010 at 2:41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant