Open
Conversation
This was referenced Apr 24, 2026
8f9dd47 to
5cd3619
Compare
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
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.
Add a new device which only supports single precision floats and does not support double precision floats.
The new device mimics torch "mps" device in that it does not have f64 but supports int64---unlike JAX which either has both or none.
dtypes,default_dtypes) device-aware;ones,emptyetc) use the device-specific default dtype when givendtype=None, device=f32_deviceTODO:
fft.{fftfreq, rfftfreq}device=arguments in internal constructionsTBD:
device2or add a newF32_device(if so, bikeshed the name)dtype=float64, device=f32_only_deviceshould raise? torch "mps" tensors raise a TypeError, follow it or mandate a ValueError?Intends to close gh-64,
Gives a way to close gh-38 --- if we have a f32-only device, we probably do not need a global flag
Addresses a large part of gh-70
Cross-ref the spec RFC to allow for missing dtypes , data-apis/array-api#998 --- note that this
array-api-strictPR can only land after the spec is updated;Also cross-ref the test suite tracker data-apis/array-api-tests#431: the test suite is actually fairly far along.