<div dir="ltr">Hey Gunnar,<div><div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="gmail-"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><ol><li>I was wondering whether the distinction between <font face="monospace, monospace">SingleContainerValueEx<wbr>tractor</font> and <font face="monospace, monospace">ManyContainerValuesExtract<wbr>or</font> is really necessary. I'm not sure if the unnecessary instantiation of an iterator in the single value case is really a problem in practice. I think extractor implementations will provide some special implementation of the <font face="monospace, monospace">Iterator</font>/<font face="monospace, monospace">Iterable</font> contract in any case. Not sure how others feel about that.<br></li></ol></div></div></blockquote></span><div>Good question. I reckon we'll know more after experimenting with this in the RI. </div></div></div></div></blockquote><div><br></div><div>I agree. The proposal mentions the possibility of having different functional rules and better performance for the single value case as reasons for the distinction. I just think that the latter one won't actually be a real problem.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="gmail-"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><ol><li>Section 2.1 states that BV will support <font face="monospace, monospace">Iterable</font> and <font face="monospace, monospace">Map</font> by default. What about <font face="monospace, monospace">Optional</font>? We will support the JDK8 date/time API, so why don't we plan to support <font face="monospace, monospace">Optional</font>?</li></ol></div></div></blockquote></span><div>Optional will be part of it by default. It should be stated somewhere, I hope :) </div></div></div></div></blockquote><div><br></div><div>The document explicitly states:</div><div><br></div><div><i> Bean Validation will have out of the box support for containers Iterable and Map.</i><br></div><div><br></div><div>I was expecting Optional to be listed here too. That's why I mentioned it. :-)</div><div><br></div><div><br></div><div>Christian</div><div><br></div><div><br></div></div><div><br></div>-- <br><div class="gmail_signature"><div>Christian Kaltepoth</div><div>Blog: <a href="http://blog.kaltepoth.de/" target="_blank">http://blog.kaltepoth.de/</a></div><div>Twitter: <a href="http://twitter.com/chkal" target="_blank">http://twitter.com/chkal</a></div><div>GitHub: <a href="https://github.com/chkal" target="_blank">https://github.com/chkal</a></div><div><br></div></div>
</div></div></div>