It is very easy to cause a stackoverflow from:

In my case I had TimeSpans because I forgot to convert them to intervals first.

I believe the intention of this code is to collect any iterators so we get vectors to hit the next method,

However:

• dispatching on the eltype of a container isn't good practice, because valid containers like Any[Interval(1,2)] won't get hit (and vcat doesn't help).
• if, like in my case, you don't have valid intervals, you should get an error, not a stackoverflow

This is extra annoying on MacOS because of the longstanding Julia issue where stackoverflows don't error properly on MacOS.

The easiest fix for the stackoverflow would be to remove the first method, however that would break any code that relies on find_intersections doing this collecting for them. I think a fix that preserves this behavior could look like:

find_intersections(x, y) = _find_intersections(collect(x), collect(y))
find_intersections(x::AbstractVector{<:AbstractInterval}, y::AbstractVector{<:AbstractInterval})  =  _find_intersections(x, y)

and then defining

function _find_intersections(x,y)
   ...
end

with what is currently in the method at