Steps to reproduce:
Search for "log(0.8)".
The result is the natural logarithm of 0.8; that is -0.22...
Search for "-log(0.8)"
The result is the negation of the base-10 logarithm of 0.8, that is: 0.097...
Expected behavior:
Search for "log(0.8)".
The result is the natural logarithm of 0.8; that is -0.22...
Search for "-log(0.8)"
The result is the negation of the natural logarithm of 0.8, that is: 0.22...
It would be OK to have the answer use the base-10 logarithm in both cases, but it should at least be consistent.
Different fields have different defaults for the meaning of "log". Signals people may often use "log" to mean base-10 log, while math/statistics people will take it to mean the base-e/natural logarithm.
Therefore, ideally, whenever the user inputs a calculation with "log", there would be a small information note saying "log was interpreted as the natural/base-10 logarithm; for the base-10/natural logarithm use log10/ln".
Debug info:
Edge/Windows 11/Europe-West2/Sweden
Image/Video: