Richard Gibson

> Do you like my proposal from the end of the issue description (Truck / Car / Vehicle instead of Dog / Cat / Pet) to achieve more clarity? Yes....

Anything addressing this issue should be required to also resolve #274, which basically stems from the fact that any bare host name is _also_ syntactically a valid URI reference (e.g.,...

This is still relevant, it just lacks a clear path to resolution.

+1 to erroring on duplicate module name.

I think it depends on the case(s) we're trying to improve. Diffs of objects with many properties, which I suspect is a principle pain point, would benefit most from hiding...

That said, I really like the dynamic collapse concept for conditionally showing excess data. But I think it would apply to lists of unchanged properties instead of whole objects/arrays, at...

Sure, but Node.js `assert.deepEqual` also ignores prototypes (among many other differences between it and QUnit). They also document [comparison details](https://nodejs.org/api/assert.html#assert_comparison_details), although this particular detail seems to be absent. But regardless,...

I'm not ready to accept this particular low-level strawman now, but I like extending `pushResult`'s argument to include diff data that overrides/replaces `actual` and `expected`. And I can see different...

I think the worker model is a good one to shoot for, implementation agnostic with respect to Web Worker or setTimeout or sibling window or iframe window or Node.js child...

> This window/iframe parallelization is probably already covered on [qunit-composite](https://github.com/JamesMGreene/qunit-composite) The core of it maybe, but the worker model I want is generic and inherently self-balancing, rather than manually pre-partitioned.