FEAT: float_power
ufunc implementation
#176
Merged
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.
Copilot Summary
This pull request adds full support for the
float_power
ufunc to the quad-precision dtype implementation, ensuring its behavior matches NumPy's expectations for floating-point types. The changes include the implementation of thefloat_power
operation, updates to documentation, and comprehensive tests to verify correctness and edge cases.Quad-precision ufunc implementation:
float_power
ufunc ininit_quad_binary_ops
, using the same implementation aspower
, since quad-precision is already a floating-point type.Documentation and release tracking:
release_tracker.md
to markfloat_power
as implemented and tested, reflecting its new support status.Testing and validation:
float_power
intest_quaddtype.py
, covering a wide range of cases including integer and fractional exponents, negative bases, zero and infinity handling, NaN propagation, integer promotion, and array operations. These tests ensure the quad-precision implementation matches NumPy's behavior for all relevant scenarios.