Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overrides #1

Open
eswdd opened this issue Sep 10, 2013 · 0 comments
Open

Overrides #1

eswdd opened this issue Sep 10, 2013 · 0 comments

Comments

@eswdd
Copy link
Contributor

eswdd commented Sep 10, 2013

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant