You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The confusion arises from such a pair of intervals being disjoint but connected sets. Maybe the error message should be changed to reflect that. Also, right now, in order to check if two intervals are disconnected, you have to do something like
isdisjoint(A, B) &&!=(endpoints(A ∩ B)...)
which is a little bit inefficient since it computes A ∩ B twice or go full-on with
AB = A ∩ B
isempty(AB) &&!=(endpoints(AB)...)
which is kind of lengthy. Maybe it would make sense to have a isconnected method?
All in all fairly minor issue, but it got me a little bit confused as a first-time user.
The text was updated successfully, but these errors were encountered:
Right now, this is the error message we get when trying to compute the union of incompatible intervals:
It is a little bit confusing since it is possible to construct the union of disjoint intervals as long as they share an endpoint:
The confusion arises from such a pair of intervals being disjoint but connected sets. Maybe the error message should be changed to reflect that. Also, right now, in order to check if two intervals are disconnected, you have to do something like
which is a little bit inefficient since it computes
A ∩ B
twice or go full-on withwhich is kind of lengthy. Maybe it would make sense to have a
isconnected
method?All in all fairly minor issue, but it got me a little bit confused as a first-time user.
The text was updated successfully, but these errors were encountered: