You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm using this library and I am very pleased with the capabilities and performance.
With vey large data to process, i see ~400K evaluations per seconds with 12 cores CPUs.
Anyway, i noticed that there is no exception thrown when doing this:
123 == "abc"
I would expect an error with this expression. Does this make sense to you ?
The text was updated successfully, but these errors were encountered:
This is a bug. It should be false based on the type alone. I'm not even sure whats happening here that the result is true.
On closer inspection i think it is correct to just return false. At first i was under the assumption the return value is "true". In my mind throwing an exception should only be done if the expression is incorrect. In this case i would go with what JavaScript does.
Hi,
I'm using this library and I am very pleased with the capabilities and performance.
With vey large data to process, i see ~400K evaluations per seconds with 12 cores CPUs.
Anyway, i noticed that there is no exception thrown when doing this:
123 == "abc"
I would expect an error with this expression. Does this make sense to you ?
The text was updated successfully, but these errors were encountered: