Comment #4 on issue 3365 by [email protected]: Patch: Create and use uniquify function for removing duplicate Grobs
http://code.google.com/p/lilypond/issues/detail?id=3365

Just a warning on this one: I'll be rereading the patch carefully again and then likely push it early. The reason is that sifting through random changes from the pixel comparisons for issue 3330 makes it hard to properly evaluate all actually actually related changes. Reviewers can't reasonably be expected to juggle with rebased branches, so I am pushing this early.

It does not remove all interaction between unrelated grobs but at least it removes the impact of memory allocation patterns on a significant part of the output phase. Impact on execution time and memory should be civil.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply via email to