Arrays must share the same dtype in meshgrid()
#298
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.
This PR clarifies that input arrays must share the same dtype.
Allowing mixed dtypes complicates both user expectations and developer implementations for the returned arrays, which is currently outlined as all having the same promoted dtype (differing from both NumPy and PyTorch behaviour). It also does not seem like anyone would use or desire input arrays of mixed dtypes.