<div dir="ltr">Yep. And speaking as someone with 250M lines of legacy, I'm well aware of the need to simplify and the need to leave things behind. See, for instance, <a href="http://wg21.link/p0684">http://wg21.link/p0684</a> - but it has to be a balance. </div><br><div class="gmail_quote"><div dir="ltr">On Wed, Apr 11, 2018 at 12:37 PM Boris Kolpackov <<a href="mailto:boris@codesynthesis.com">boris@codesynthesis.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Titus Winters <<a href="mailto:titus@google.com" target="_blank">titus@google.com</a>> writes:<br>
<br>
> Yeah, one of the recognized strengths of C++ is that it doesn't leave all<br>
> of the legacy code behind, generally speaking.<br>
<br>
But there is a cost to this legacy support both in time it takes<br>
the committee to figure out the battalions of special cases as well<br>
as the resulting complexity which some of us have no capacity to<br>
handle and which will most likely limit the "toolability" of the<br>
end result.<br>
<br>
Boris<br>
_______________________________________________<br>
Tooling mailing list<br>
<a href="mailto:Tooling@isocpp.open-std.org" target="_blank">Tooling@isocpp.open-std.org</a><br>
<a href="http://www.open-std.org/mailman/listinfo/tooling" rel="noreferrer" target="_blank">http://www.open-std.org/mailman/listinfo/tooling</a><br>
</blockquote></div>