-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
about duplicate constraints #160
Comments
@sccolbert may have a better intuition on this one... I will try to look into it though, but feel free to ping if you see by the end of may. |
The solver only tries to protect you from adding the same constraint
*object* more than once, because the internal data pointer they hold needs
to be unique in the system.
It doesn't try to figure out whether two different constraints are the same
equivalent constraint, because that would take a lot of extra processing
for little gain, and it will not affect the solution to the system.
…On Sat, Apr 29, 2023 at 11:16 AM Matthieu Dartiailh < ***@***.***> wrote:
@sccolbert <https://github.com/sccolbert> may have a better intuition on
this one...
I will try to look into it though, but feel free to ping if you see by the
end of may.
—
Reply to this email directly, view it on GitHub
<#160 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABBQSNKRMZNGANOVSGMDL3XDU5GVANCNFSM6AAAAAAXJJGDMU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks @sccolbert |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
The following code snippet does not throw DumplicateConstraint:
From the implementation I can see why it doesn't throw, but I wonder whether should this scenario also be considered as a duplicate constraint?
The text was updated successfully, but these errors were encountered: