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
Unioning AtomicInterval instances (and by extension Interval instances) can lead to an invalid result if the two intervals share a (lower or upper) bound, where one is open and the other one is closed.
>>>I.closed(0, 2) |I.open(0, 2)
I.open(0, 2)
... where the expected result is I.closed(0, 2).
The text was updated successfully, but these errors were encountered:
This issue is fixed in the master branch, and the fix will be part of 1.9.0 update or, if I cannot manage to release this version soon, will be hotfixed in 1.8.1.
Unioning
AtomicInterval
instances (and by extensionInterval
instances) can lead to an invalid result if the two intervals share a (lower or upper) bound, where one is open and the other one is closed.... where the expected result is
I.closed(0, 2)
.The text was updated successfully, but these errors were encountered: