SingletonCObject class?

[mweidner037]

This would be a CObject with a single child. It would permit optimized messages and saves (no name needed), and might simplify subclass implementations.

Perhaps equivalently: think of as a Collab decorator?

E.g. the "layers" often have a single child.

One caution: for classes that might add more children later, this could make Cambria-style versioning more difficult.

[mweidner037]

This seems like an unnecessary optimization.