infinite loop on _interval_.filter about d3-time HOT 2 CLOSED

I think the answer here is “don’t do that”. I don’t see what we could do differently since interval.range is built on interval.offset, and if interval.offset hangs because the filter never returns true, there’s no way to avoid the infinite loop. Also practically speaking, fixing this doesn’t seem urgent since people can write their custom intervals accordingly to avoid the infinite loop (and custom intervals aren’t very common).

from d3-time.

yup, I was looking at the code and realized there's no easy way to prevent that from happening; you find it soon enough when you make the mistake ;-)

from d3-time.