Imported From: https://issues.scala-lang.org/browse/SI-3621?orig=1
Reporter: @oxbowlakes

@oxbowlakes said:
Oops - sorry for the bad link to the first bullet point

@axel22 said:
Working on it.

One thing troubles me, though. Why do you want to mark the method as transient? Looking through the Java language and vm specifications, and browsing all around the net, I couldn't find a reference for the transient modifier being applied to methods and what that means.

@oxbowlakes said:
As far as I was aware, Java used the transient modifier within the bytecode to mark a method which takes an array as being a varargs method.

I now cannot find any reference to this, so I am presumably wrong. However, IDEA will mark a varargs method in a class file as being "transient", so perhaps that's the source of the issue.

@oxbowlakes said:
I take it all back - this is easily testable as follows:

import java.lang.reflect.Method;
import java.lang.reflect.Modifier;

public class VarargsTest {
public static void main(String[] args) {
for (Method method : VarargsTest.class.getDeclaredMethods()) {
System.out.println(method.getName() + " " + ((method.getModifiers() & Modifier.TRANSIENT) > 0 ? "TRANSIENT" : ""));
}

}

public static void foo(String[] ss) {
    System.out.println("ss = " + ss);
}

public static void bar(String... s) {
    System.out.println("s = " + s);
}

}

@axel22 said:
Interesting. In fact, I was wrong - it seems to be documented here:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6516895

Ok, then so be it.

@dcsobral said:
Wasn't this closed by r23578?

@axel22 said:
I'm still waiting for the review.

@paulp said:
I reckon that's all the reviewin' we're gettin'.