-
Notifications
You must be signed in to change notification settings - Fork 492
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
Getting "mismatched type to binary operator" for int64/int64 or float64/float/64 in 0.13 #561
Comments
@mtslzr We significantly changed the implementation of lambda expressions in 0.13 so something like probably messed up somewhere. I'll take a look. |
@mtslzr I can't reproduce this locally, could you share a more complete example where you are getting this error? Thanks. |
@mtslzr I figured it out, and I am chasing down the bug now.... |
@nathanielc what's the bug? Sounds very weird bug.. |
@yosiat I just posted the PR #567 Besides some refactoring of the error messages, it boiled down to |
Working a script for checking memory usage. We pull total and used (in bytes) from InfluxDB, so I need to generate the percent myself. In 0.12, I was able to do something akin to this, an example of usage being over 50%:
Unfortunatley, since 0.13, damn near any combination of the above (using float or int) results in an error like this:
Still learning this, so my gut say it's something silly I'm missing, but I can't seem to figure it out.
And FWIW, I've managed to get similar errors for float64 > float64, int64 / int64 and int64 * int64.
The text was updated successfully, but these errors were encountered: