> Looking at the PR, there is one thing I have a 'bad feeling' with. > And that is that everything is done in an eager way. > E.g. we now maintain another list, the contentModel, even if you don't need > it. > I see why this API can be useful. And I even needed something like this, just > not very often. > Performance wise this should not make a big impact, still something we may > should discuss here.
It would add something on the order of 80-160 bytes to every `Parent` instance, assuming compressed references. For reference, a Property weighs in at about 40 bytes. In an application with 10,000 nodes in the scene graph, that's about 1-2 MB of extra memory. While I agree that we should always keep memory usage in mind, I think this won't make or break this feature.
