-
Notifications
You must be signed in to change notification settings - Fork 250
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
[Core] Consistency between Element/Condition and Node clone #4795
Comments
I think this discussion is still valid |
@KratosMultiphysics/technical-committee |
@loumalouomega We are currently considering options to "merge" elements and conditions. As long as the PR is ready we will ping everyone. In the meantime, I agree with you, its odd that they have different interfaces :S |
It is nice to unify elements and conditions, as implementation is 99.9% identical. In any case, this discussion is still valid. |
@KratosMultiphysics/technical-committee don't see any reason for having the Clone method for the node as we don't derive from it. So we propose to remove the Clone of the node (and implicitly we don't have inconsistency anymore) |
@loumalouomega is this still a relevant PR in view of eventually removing the clone of the node? |
There is a PR, where this is discussed as well |
(@RiccardoRossi you contributed recently there) |
The clone of the node does not consider new Id:
Kratos/kratos/includes/node.h
Line 328 in fbb7be7
But the condition and element does:
Kratos/kratos/includes/element.h
Line 233 in 231a4d1
Maybe we should discuss this inconsistency
The text was updated successfully, but these errors were encountered: