Skip to content
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

Shouldn #16

Closed
geeohgeegeeoh opened this issue Nov 12, 2019 · 3 comments
Closed

Shouldn #16

geeohgeegeeoh opened this issue Nov 12, 2019 · 3 comments
Labels
invalid This doesn't seem right

Comments

@geeohgeegeeoh
Copy link

geeohgeegeeoh commented Nov 12, 2019

>> import intervals as I
>> x = I.open(int(1), int(3))
>> y = I.open(int(4), int(5))
>> x|y
(1,3)|(4,5)

these are open intervals, the bounds are defined as Int instances. So, unlike reals, the two integers abut, there is not an infintity of real points or intervals between them. Surely the result of x|y should be a singleton which is the extend of x.left and y.right not the explicit x|y outcome?

If I coerce this as (1,3) | (3,5) it works. So for the bounds matching it works. It feels like the difference between open and closed intervals has been lost here.

@AlexandreDecan
Copy link
Owner

Please read the doc, we do NOT support discrete intervals.

@geeohgeegeeoh
Copy link
Author

geeohgeegeeoh commented Nov 13, 2019 via email

@AlexandreDecan
Copy link
Owner

There are some libraries that support discrete intervals, e.g. https://pyinterval.readthedocs.io/en/latest/guide.html

However, they have their own set of issues, and most of them are not maintained anymore...

@AlexandreDecan AlexandreDecan added the invalid This doesn't seem right label Dec 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants