<div dir="ltr">@Gunnar<div>I agree that is better to omit (until clarification) the array problem from the spec.</div><div>Could you give a try contacting the spec lead for the JDK, as suggested by Michael and Emmanuel, to see if a (future) clean solution is possible?<br><br>From a more realistic perspective (seeing the schedule and what happens in other JSR) I think that the solution you and Guillaume suggested (backward compatibility and wait for the 2.1) doesn't have many alternatives. </div><div><br></div><div>Thanks</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 19, 2017 at 10:07 PM, Michael Nascimento <span dir="ltr"><<a href="mailto:misterm@gmail.com" target="_blank">misterm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Wed, Apr 19, 2017 at 4:27 PM, Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>But<div> @Target(FIELD, TYPE_USE)</div><div> @interface Size</div><div> </div><div> @Size(2) String[] arrayOfTwoStrings;</div><div><br></div><div>is ambiguous in Java 8</div></div><div><br></div><div>So the JLS is “backward compatible” in the language designer’s view I suppose. </div></div></blockquote><div><br></div></span><div>When you don't change, it's backward compatible indeed. When you do, the language design is flawed. So there is a hole in one combination that needs to be addressed. Joshua Bloch would write about that all the time, of how new features interact in unexpected ways and that's why you have to resist changes in the language.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>They did not anticipate people wanting to add TYPE_USE to an existing annotation and have a side effect on its usage on arrays.</div></div></blockquote><div><br></div></span><div>Exactly, so this is effectively broken and needs to be fixed in the language, not in BV. But I'm still afraid we might have got something wrong here, so I would rather ask them.</div><div><br></div><div>Regards,</div><div>Michael</div></div><br></div></div>
<br>______________________________<wbr>_________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org" target="_blank">beanvalidation-dev@lists.jboss<wbr>.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailma<wbr>n/listinfo/beanvalidation-dev</a><br></blockquote></div><br></div></div>