Meh, perhaps my use case is a bit of an abuse/edge case, anyway? I think I’d shoot down my own ticket. I’ll see about clarifying and making one if you like though.

Sweet. It was hard to sell this as our js testing, when it didn’t work with some of the more important browsers we support.

I meant to comment here. See below.

So this check prevents one from doing stuff like overloading eql? and == for custom collection behavior.