markmandel/mxunit — comment on commit beab9c837a17ff4f7123942f54bcf62a0e91c5a2
File:  line 0
By d1rtym0nk3y:

The original behaviour of throwing when trying to compare arrays was informative if slightly inconvenient. i'd worry that this change will cause unexpected results and provide no feedback

I think i'd be in favour of keeping the original behaviour, and as arrays are a "special case" in CF, creating assertArraySame / assertArrayNotSame methods, and instructing users to use these methods in the throw message.