Unexpected behaviour when combining Equivalent and LCS options

[will-isovalent]

I would have expected to be able to use these together, however it seems that they are mutually exclusive based on a cursory look at the code and some experimental results. The behaviour I have in mind would be something like: do Equivalent comparison and then fall back to LCS if the arrays are not equivalent.

[wI2L]

You're right, compareArraysLCS ignores the Equivalent() option.

That's mostly an oversight on my part, the lengths of the source and target arrays can be compared and if they are equal, deeply compare them before doing the LCS diff.

I'll add this in the next version. Thanks for the report.

[will-isovalent]

Awesome, thank you for the quick reply.