feat!: return tuples rather than lists in meshgrid, broadcast_arrays, and info.devices
#981
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 PR
meshgridto return atuplerather than a list. This follows NumPy and PyTorch.broadcast_arraysto return atuplerather than a list. This follows NumPy.info.devicesto return atuplerather than a list. This ensures consistency with the rest of the specification where we always returntuples, rather than lists.This changes benefits Array API consumers such as Numba, where working with tuples facilitates optimizations.
Note that this is a breaking specification change.