Skip to content

Conversation

SwayamInSync
Copy link
Member

This PR refactors the constants exposure and provides the initial finfo support based on the upstream numpy.

NOTE: In order for this to pass CI, need to build numpy from source. Will do that in follow-up PR

Copy link
Member

@seberg seberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: In order for this to pass CI, need to build numpy from source. Will do that in follow-up PR

You can probably just add the nightly build to the index: https://scientific-python.org/specs/spec-0004/#test-with-nightly-wheels and then assume that for building.

I dunno if you are OK with a strict NumPy 2.4 requirement, but I suppose for quaddtype it may be just as well.

}

/* Store the Sleef_quad value to the provided pointer */
*(Sleef_quad *)ptr = val;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you support unaligned, should use memcpy, unfortunately. (Or we change that we promise to not call it for unaligned stuff, which I can get on-board with.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually thinking about it, I am not sure if this is true or not :), we needed copyswap anyway due to byte-swapping. I am actually happy to say that the data must be aligned.

@SwayamInSync
Copy link
Member Author

You can probably just add the nightly build to the index: scientific-python.org/specs/spec-0004#test-with-nightly-wheels and then assume that for building.

Right, I was also thinking to make nightly the default build as right now or maybe even in future this repo will directly be using the upstream features (if some modifications be needed from NumPy side)
I might not be able to see the point in using different versions and then putting conditional checks everywhere in code to enable/disable features

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants