This is an insidious bug rooted in how we parse floating point numbers, combined with a caching-related problem that causes the order of 0.1e0 vs 1e-1 to matter for all further outcomes.
I wasn't able to find a ticket for this in our bug tracker, but it most definitely is something we will fix.
