I figured the terse error message would be worth it considering the code involved in a custom matcher. I suppose I could split it into two tests, e.g. `expect (a).not.toEqual(b); expect(b).not.toEqual(c);`