-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Cleanup Math
methods
#514
Comments
I’ll take this |
Sure! |
@HalidOdat There are still some methods that can be cleaned up in this issue. I just did the ones that were quick and easy. |
In that case, I'll reopen the issue :) |
In that case, we might benefit from mapping which methods still need refactoring:
|
There are a couple of these functions that are not yet implemented. Are there separate issues tracking the implementation of those functions? |
we don't have an issue for tracking the unimplemented ones. I'll create it :) Edit: #524 |
Many of the Math builtin functions are a bit convoluted for example:
This is also inefficient because we check if there is an argument and then another check is done when we call
.expect()
.A better way of doing this would be to use
.map_or
which would simplify the code a lot:The text was updated successfully, but these errors were encountered: