<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Because many APIs use configuration/partial initialisation patterns. Look at Metal for example. But I agree that most of the time, its not such a big deal. <div class=""><br class=""></div><div class="">— Taras<br class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 13 Apr 2016, at 17:34, Kurt Werle <<a href="mailto:kurt@circlew.org" class="">kurt@circlew.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra">I've always thought that the with construct is not a good idea. It seems to me that the moment you want to use with it indicates that you are getting too much into some other classes business; shouldn't that class deal with this? Why are you exposing/integrating so much of some other class's logic? Maybe there should be a method that does all this, or maybe a custom struct that passes all the appropriate information...</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">Yeah, there are exceptions - always. But for the most part I'm not a fan.<br clear="all" class=""><div class=""><br class=""></div><div class="">Kurt</div>-- <br class=""><div class="gmail_signature"><a href="mailto:kurt@circlew.org" class="">kurt@CircleW.org</a><br class=""><a href="http://www.circlew.org/kurt/" target="_blank" class="">http://www.CircleW.org/kurt/</a><br class=""></div>
</div></div>
</div></blockquote></div><br class=""></div></div></body></html>