Hi Dimitris,
Thank you for your response. The main rationale is to be able to determine a model's state. When given an IModel reference it is currently impossible to know whether it is safe to query it because there is no way to know if load or dispose has been called. The only option is to try allContents, for example, and catch an exception. This is very inefficient however.
If backwards compatibility is a concern perhaps we could make it a default method and throw new UnsupportedOperationException, but for any IModel which implements load and/or dispose this method is trivial to implement and should be implemented.
I think Betty and Horacio or others may also want to chime in here with their use cases as it's something I recall being discussed before.
Thanks,
Sina
Hi Sina,
Thanks for the proposal and for investigating its impact. Could you
briefly summarise a couple of use-cases for this new method? As this
will be a breaking change (any EMC drivers that we don't control will
produce compilation errors) it'd be useful to have some justification
on record.
Thanks,
Dimitris
