Leo Fang

I'd keep at least `bits` and `eps` for `cinfo`, but definitely exclude `min` and `max` because we don't wanna follow NumPy to define some awkward comparison/sort capabilities over complex-valued arrays...

I am revisiting this issue as I encounter a similar need. Parallel to the need for updating docstrings (#180), we also need this metadata to populate, say TOC of a...

Complex number support was raised in #102. I should have added eigensolvers being another big application there! 😞 Thanks for raising this need again, @kgryte.

One thought following the resolution https://github.com/data-apis/array-api/pull/105 could be that we still accept this PR to define the signatures clearly, but say that the actual standardization will come along with the...

One thing interesting (which I mentioned in today's meeting) is that ROCm currently does not provide an eigensolver for general Hermitian matrices, only for tridiagonal matrices: https://rocsolver.readthedocs.io/en/latest/userguide_api.html#eigensolvers.

Thank you for the detailed research @steff456! I haven't read this very carefully, just leaving a note. From the perspective of scientific computing, image and signal processing, etc., I'd like...

Based on the conversation in the meeting last week, we discussed: 1. `scipy.fft` is missing from the table, but it's a superset of the NumPy API, with all extra functionalities...

> To add to Ralf's point, I think there is an [MPI FFT library](https://mpi4py-fft.readthedocs.io/en/latest/). Not sure if we want to look at that as well AFAIK mpi4py-fft provides both a...

> 3\. @leofang proposed to not add `fft2`/`ifft2` (and other 2D families), as it's just a special case for `fftn`/`ifftn`. No one objected, but it's best to solicit feedbacks from...

Hello'all, I just came up with a wild question while reviewing #189. I am curious if we can remove `fft2`/`ifft2`, is it really necessary then to special-case 1D transforms from...