<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jun 11, 2014, at 11:29 PM, deadal nix <<a href="mailto:deadalnix@gmail.com">deadalnix@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">It is gonna improve the situation quite a lot for all frontend that use aggregate loads (arguably, that is a bad practice, but that no reason to stab people in the back when they do it anyway).</span><br></blockquote><br></div><div>I’m not sure I agree with that statement. If we don’t think they should be used, not optimizing them is a good way to discourage that. More generally, I’m concerned about how we will ever get good test coverage of this code path, since we don’t have any extant front ends that hit it.</div><div><br></div><div>—Owen</div></body></html>