Add ThickNumbers extension - #770
Conversation
ThickNumbers.jl (https://github.com/HolyLab/ThickNumbers.jl) provides a general interface for "numbers with width," of which intervals are the premier example. Other examples include Gaussian random variables and other implementations of "fuzzy numbers." While this does not make this package's intervals a subtype of `ThickNumber`, it does add a compatibility shim that is sufficient for at least one tested non-trivial consumer.
| # `in_interval(::Interval, ::Interval)`, a real point's membership in an interval is always | ||
| # decidable, and `IA.in_interval` already computes exactly that (`Base.in(::Interval, | ||
| # ::Interval)` is the one IA purposely leaves unsupported, for `issubset_interval` instead). | ||
| Base.in(x::Real, a::IA.Interval) = IA.in_interval(x, a) |
There was a problem hiding this comment.
This looks like type piracy, no?
There was a problem hiding this comment.
In the sense that this method has nothing to do with ThickNumber, and the package extension does not own Interval. In any case, it's probably not a feature we'd want to add to IA.jl.
|
Aside from my comment on |
|
Thanks. To explain: I'm deliberately dragging my feet on this. I want to make it the last of this sequence of changes, because I don't want to saddle you with something that needs maintenance but which no one actually uses. #778 is the only real thing I'm waiting on here. I'm also thinking of making breaking changes to ThickNumbers to bring it into better compliance with the choices made here. #779 is not blocking me, I just noticed it and think this is a rare case where ThickNumbers may have gotten to a better answer than IA. |
2 participants
ThickNumbers.jl (https://github.com/HolyLab/ThickNumbers.jl) provides a general interface for "numbers with width," of which intervals are the premier example. Other examples include Gaussian random variables and other implementations of "fuzzy numbers." While this does not make this package's intervals a subtype of
ThickNumber, it does add a compatibility shim that is sufficient for at least one tested non-trivial consumer.