-
Notifications
You must be signed in to change notification settings - Fork 251
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
questions on interfaces behaviour #29
Comments
The exact behavior of this method should be checking for owning status and delete the element if necessary. If T is not a pointer, it is not necessary. But for the Vector case, what I was thinking is that if I can pass a pointer to the container, then I at least have a reference of the object and if I want to remove it from the container then I may not want to invalidate my reference at the same time. So the behavior here is not standard but it is reasonable. I don't know how to reconcile this obvious conflict. Do you have any idea? |
If Globally, I think that the library must have consistent, non-contradictory API throughout all the code base. Ideally, all these caveats must be documented, or at least (which is more important) all derived classes must display the same behaviour hinted by their ancestors. |
OK, I think you are right. I will fix the inconsistency ASAP. |
Hi, any success? I'd be glad if you process the PR backlog out there 😄 |
Not yet. Sorry for the slow response to your PR. I am extremely busy since I changed my job... I will try to process your PRs tonight. Thanks for your contribution. |
Must the method implementation check for
m_owned
and doSafeDelete()
?mql4-lib/Collection/Collection.mqh
Line 136 in e7608fb
For example, here, you say:
mql4-lib/Collection/Vector.mqh
Line 112 in e7608fb
What's the expected behaviour here?
The text was updated successfully, but these errors were encountered: