You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A thought just occurred to me re virtualheap. Does CO support overriding a named field with another (i.e. In a MapNode can you simply override one child with another with the same name)? In the MapNode code it looks like you can, so I was wondering if there's anything in Cougar that prevents this.
If it is possible, is it strictly allowed? Presumably all descendants of the overridden child should be removed from the heap, but as it is I don't think that's the case? Maybe we could either strictly forbid overwriting, or if we want to supper it ensure the system handles it robustly. Maybe have new Updates, OverwriteField (and OverwriteIndex, which currently is impossible)
The text was updated successfully, but these errors were encountered:
From Tom:
A thought just occurred to me re virtualheap. Does CO support overriding a named field with another (i.e. In a MapNode can you simply override one child with another with the same name)? In the MapNode code it looks like you can, so I was wondering if there's anything in Cougar that prevents this.
If it is possible, is it strictly allowed? Presumably all descendants of the overridden child should be removed from the heap, but as it is I don't think that's the case? Maybe we could either strictly forbid overwriting, or if we want to supper it ensure the system handles it robustly. Maybe have new Updates, OverwriteField (and OverwriteIndex, which currently is impossible)
The text was updated successfully, but these errors were encountered: