On Thu, Oct 18, 2012 at 5:39 PM, Basurita <basuraparabarspi@xxxxxxxxx>wrote: > I seem to remember Mike saying that a print() call will abort the trace, > so that trace won't be compiled (or something like that!!) > That may explain why things work correctly when you add the print(). He > mentioned something along the lines of using io.write() instead... > Right, but it does not seem applicable for this case however. The print statements do not make it work (it still fails seemingly erratically), they just illustrate that the condition above should not have evaluated to true and that __eq is not called. Cheers, -- Nils Nordman <nino@xxxxxxxxxxx>