Steve Gravrock

A caller-supplied cloner function makes sense to me. If you're still interested, I'd be happy to review a PR that adds that feature.

Is this something that you'd want to leave on all the time, or would you just turn it on in certain situations? I'm wondering if some UI like a link...

Understood. My main concern with anything like this is that people sometimes forget that they're running focused. I don't want to add any risk of people thinking that their suite...

Do you need the DiffBuilder iteslf, or would a method that's like [MatchersUtil#equals](https://jasmine.github.io/api/edge/MatchersUtil.html#equals) but also gives you the diff work? I'd prefer not to expose DiffBuilder itself at this point....

Great. Just to firm this up a bit, here's Jasmine's own toEqual matcher rewritten to use the API I'm thinking of. ``` function toEqual(matchersUtil) { return { compare: function(actual, expected)...

Closing due to inactivity.

> Why was this closed? As I said, inactivity. I routinely close issues when the reporter doesn't answer follow-up questions and nobody else expresses interest. Otherwise the issue tracker would...

I can see the usefulness of this feature, but I'm not sure how to implement it reliably and portably. Jest has the advantage of only needing to deal with Node....

@nicojs I appreciate you taking the initiative to tackle this. Doing the stack trace processing in a library makes a lot of sense in principle. But Jasmine isn't currently set...

Most spec files aren't ES modules, and I don't expect that to change for the foreseeable future. However, while we can't assume ES modules, we *can* make a lot more...