On Thu, Feb 16, 2017 at 04:34:35PM -0600, Roland Haas wrote:
I asked the same question and (par for the answer is): it is at parsing it with both methods and then comparing so it must be strictly slower :) This also qualifies for "debug code" I guess.
The idea is to catch cases where the new parser gets to a different result than the old, especially for thorns we don't have access to. I wouldn't call it 'debugging', since there is nothing to debug at the moement, maybe verification - but that is just a name anyway.
The more interesting question is: how much slower did it get for individual users - and was it piraha or something else? It shouldn't be much more than twice as slow, because otherwise it would mean piraha would be slower than the old method. It would still be better than the old method, and it was never meant as a replacement for efficiency reasons, but it would be interesting to know what the difference is.
Steve (I know you are out of town, but at some point you are going to read this): is there an easy way to temporarily disable one or the other method, so that a speed-test could be made by anyone, on their system, with their thorns?
Frank
signature.asc
Description: Digital signature
_______________________________________________ Users mailing list [email protected] http://lists.einsteintoolkit.org/mailman/listinfo/users
