-
-
Notifications
You must be signed in to change notification settings - Fork 426
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
Change in behavior in 1.15 with in
and float64
#426
Comments
I see. The type checker got more strict, looks like in this case, we can bring back int->float conversion. |
@zachaller Also what about adding Argo's expressions test corpus to directly to expr? For example, here are expression tests for CrowdSec:
This way we can prevent such regressions in the future. |
Yea, I will spend some time looking into this and opening a PR! |
Fixed. Let's add Argo expression corpus for repression testing 😉 |
In argo rollouts we had our tests starting to fail on 1.15 it seems that we needed to be explicit in converting to floats which we did not have to before here are two examples.
1.14.0: https://goplay.tools/snippet/gaA2hxV9auw
1.15.0: https://goplay.tools/snippet/rZsOUyfRRop
Working in 1.15.0 with explicit casting: https://goplay.tools/snippet/XBqyWpRfj6I
Is this expected behavior?
The text was updated successfully, but these errors were encountered: