-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Generic test for allowing to use isless #319
Comments
@nalimilan - following the discussion on Slack what do you think of requiring a wrapper around non-categorical value when doing I guess |
Yes I think that would be OK. That type could also be useful when returning a value from |
I would argue this behavior is perfectly fine. That is the definition of a partial order: not every pair of elements can be compared. Forcing users to only use a total order is strictly less expressive. |
We do not have much room here for discussion. The contract for
so it is not allowed to define |
Consider the following example:
This behaviour is very problematic I think. The reason is that given two containers
x
andy
there is no way to check if you can safely useisless
to compare their elements. I could run a strict check ifeltype
ofx
andy
are the same, but it is not desirable very often (e.g. numbers can be compared even if their type is different).The text was updated successfully, but these errors were encountered: