Grumble: performance hit using String.ToDouble vs Val

[Mike_D]

@Keith_Culotta

It looks like toDouble does some cleanup of the string parameter before it gets evaluated, which might explain some of the performance hit.

Yes, see Xojo1BRC (Xojo One Billion Row Challenge) - #14 by Mike_D
where I noted:

From this you can see the hottest method is in the String.ToDouble() method, which appears to have a lot of string processing inside it (including a call to ReplaceAllText which perhaps should be reported as a separate bug?)

I wonder if the ReplaceAllText is converting commas to periods before parsing? I’m sure that could explain part of the 5x slowdown.