It appears the plain overloads of Arrays.toString cannot be used to
provide an annotation source compatible form since they use "[]" rather
than "{}" to surround to contents. I'll see if I can handle that.
On 7/28/2016 8:33 AM, Rafael Winterhalter wrote:
Another remark about "printability". Arr
Another remark about "printability". Array types are printed in their
internal form, i.e. "java.lang.Void[].class" becomes
"Ljava.lang.Void;.class" in the string form.
While I very much agree over the improvements of the toString
implementation of the unresolved values, I still wonder if this spec
Hi Joe,
thank you for your answer. Can I ask for the rationale of using {} instead
of [] only for classes? If the goal was to come closer to the source code
representation, would this not imply to use curly braces for all array of
an annotation?
Thank you for your time! Best regards, Rafael
2016-0
Hello Rafael,
On 7/18/2016 5:43 PM, Rafael Winterhalter wrote:
Hello,
I recognized a failing test on Java 9 caused by a changed return value
returned by toString on an annotation with a class-property.
When calling toString on an annotation: @interface Foo { Class value();
} instantiated as @Fo
