Skip to content
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

Refactor library to use float32 instead of float64 whenever possible #32

Open
Xkonti opened this issue Oct 4, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@Xkonti
Copy link
Owner

Xkonti commented Oct 4, 2023

Operations on float64 are more expensive than on float32. The library should be refactored so that float64 is as limited as possible. Things to consider:

  • cost of converting from float64 to float32 to perform further operations. It might be cheaper to continue with float64 in between areas where float64 is required.
  • If the return type of the function is not float64 the conversion cost might be considered free as it would need to happen at some point anyway.
@Xkonti Xkonti added the enhancement New feature or request label Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant