Olivier Hénot

@schillic @agerlach I do not think anyone got around to fix this. In fact, there are some discussion about restricting the bounds of `Interval` to `AbstractFloat` (see e.g. #495). It...

That definitely sounds useful! Thanks for chiming in. > Side note, we could always define > ``` > const FloatOrRat = Union{AbstractFloat, Rational} >``` Seems like a good idea. >...

I am closing this issue since `@interval` has been removed (and if it were to be reintroduced later, it will just be a syntax sugar to wrap every constant literals...

@lbenet I was looking into fixing this issue for the 1.0-dev branch, but I realized that I am not reaching the same conclusion as you. The interval arithmetic formalism can...

I may be misinterpreting Note 1 in Section 10.2 of the standard which is: > NOTE 1 — The definition implies −∞ and +∞ can be bounds of an interval,...

I mean I do understand your point of view (and thanks for taking the time to discuss this). Indeed, the clause is contradicting itself 😄. But, as you said, I...

Interesting I have not looked into the "Cset flavour". I focused on the "set-based flavour" because that is the main one on the 1.0-dev and we need to decide on...

> I agree that it is uncomfortably hard to think `Inf` differently, when it is used as a floating point, and when it is used as an end-point of an...

Ah I think I found a potential tie-breaker: `(-1..1)/Inf == [0, 0]` or simpler `(0..0) * Inf == [0, 0]`. If this is imposed by the standard, then `prevfloat(Inf)..Inf` is...

Sorry I should have made this clear in my previous comment: $0 \times \infty$ is indeterminate so `(0..0) * Inf == 0` is wrong, the result should be either to...