-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unintuitive use of ≈ #140
Comments
This is tricky, because these situations are pretty much estimations, that are accurate enough to be completely correct in a lot of cases. In the first example, it should be possible to verify that it's correct though, so that shouldn't be too hard to improve. In the second one, I'm a bit uncertain. If you type At the moment, I feel like the second example makes a bit more sense than the first one, because it says that the result of the calculation is |
What do you think about starting all responses with
Or when it can be verified to be exactly sqrt 8, it should be reordered like this:
|
That could make sense. It could use this one returns a lot of decimals, meaning it gets rounded before printing, so a
this one just returns an integer, so it doesn't get rounded:
and these can be verified:
Yeah I think this would be doable |
Sounds good! But maybe your last three examples should still start with a
|
And for the first example in my screenshot, it should say |
Equations are still going to be displayed as approximations for now, since they are sometimes rounded off at the end, and equations would be verified before that stage, so it's going to require some more work. I think the other things mentioned have been implemented though. |
@timokoesters You may be interested in the following discussion: “Subtracting a value from itself equals not zero”. The output used to be way scarier. $ kalker204.exe 128.36+126.86-255.22
1.4210854715×10^-14 ≈ 0
$ kalker220.exe 128.36+126.86-255.22
= 0
$ qalc.exe 128.36+126.86-255.22
128.36 + 126.86 - 255.22 = 0 |
Kalker writes ≈ even though the result is exact, but often presents other results as if they are exact
The text was updated successfully, but these errors were encountered: