3 ms·
I've been getting erroneous unit conversions for half a year now - https://www.google.com/search?q=130m+to+inches https://www.google.com/search?q=130m+to+inche
by ortusdux 2y ago
I've been getting erroneous unit conversions for half a year now -
https://www.google.com/search?q=130m+to+inches https://www.google.com/search?q=130m+to+inches
Interestingly, "130m to in" works
https://www.google.com/search?q=130m+to+in https://www.google.com/search?q=130m+to+in
- IshKebab 2y ago"130m in inches" works. I'm pretty sure that's the "native" syntax and anything else is fed through some kind of heuristic recogniser which obviously didn't work in this case. Very strange failure mode though!
- ortusdux 2y agoDifferent values with the same syntax will pass/fail randomly: https://www.google.com/search?q=130m+to+inches https://www.google.com/search?q=130m+to+inches https://www.google.com/search?q=140m+to+inches https://www.google.com/search?q=140m+to+inches Return 51.1811" and 5511.81" respectively
- IshKebab 2y agoYeah, as I said I think that's because "to" is not the right syntax, so it fails the "native" calculator input and has to get translated into the proper syntax by some probabilistic system.