"m...@mikesolomon.org" <m...@mikesolomon.org> writes: > As was the case in a few of my previous projects, before I start > something new I make architecture changes that facilitate my work. > Working on 2801, I've realized that any multi-pass algorithm for the > spacing of grobs is difficult because results of callback calculations > are always cached. So triggering callbacks a second time is, in the > current architecture, impractical and requires a fair bit of kludgery.
[...] > performance is uncertain, but it'd probably require more optimization > in skyline.cc and/or caching of skylines. It sounds to me like you consider caching a bad idea so you want to remove it, and to make this removal feasible you think you will be required to do caching. It sounds to me like it would make more sense that we improve our cache invalidation strategy where it goes wrong rather than shifting the problem around in increasingly complex manners. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
