<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 4, 2012, at 5:16 PM, Mike Lawther <<a href="mailto:mikelawther@chromium.org">mikelawther@chromium.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On 5 September 2012 09:44, Dirk Schulze <span dir="ltr"><<a href="mailto:dschulze@adobe.com" target="_blank">dschulze@adobe.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It is very likely that even future code will land with this operator instead of StringBuilder.</blockquote><div><br></div><div>Not if Adam removes the operator as he proposed earlier :)</div><div><br></div><div>If operator+= cannot be made sufficiently efficient, we could always leave the operator there, but have it ASSERT with a message saying to use StringBuilder.</div></div></div></blockquote><br></div><div>Please not this. Failing at compile time is much better than failing at runtime in debug builds only.</div><div><br></div><div>Cheers,</div><div>Maciej</div><div><br></div></body></html>