Comment #26 on issue 2990 by [email protected]: \RemoveEmptyStaves in
StaffGroup context crashes
http://code.google.com/p/lilypond/issues/detail?id=2990
Now we're talkin'
I think some sort of efficiently implemented tree would be a great idea.
The issue is that there are a few levels of data to hack trough. Grob
arrays contain grove, which have properties, which themselves may be Grob
arrays. So, one still needs to pass through the property or object lookup
mechanism. If there is a way to implement a tree data structure while
preserving the core Grob/property model, I'm all for it.
