feat(precision): add f32 floating-point precision support #10
+222
−151
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add optional f32 floating-point type support while maintaining f64 as default - Update type annotations in function signatures from f64 to TAFloat - Add comprehensive documentation in advance.md explaining precision options - Fix examples to work correctly with flexible precision types - Update version to 0.2.1 to reflect the new feature This change allows for reduced memory footprint for large datasets when f32 precision is sufficient for technical analysis use cases.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change allows for reduced memory footprint for large datasets when f32 precision is sufficient for technical analysis use cases.