Athan

@mhkeller For alternatives, see https://github.com/stdlib-js/stats-ttest and https://github.com/stdlib-js/stats-ttest2.

In projects that I work on, we'd also like to be able to install only one package (or a subset of packages) without needing to install the whole dependency tree...

Another use case we have is that we periodically need to investigate issues in older Node.js versions which are not officially supported. Various dependencies may have dropped support for such...

Based on the most recent consortium meeting (2022-06-23), consensus was not to move forward with this proposal. However, we would like to look into the possibility of providing generic APIs...

Tracking changes to existing APIs within the array API specification: - [x] Data Types: `complex64` and `complex128` - - [x] Type Promotion Rules (including mixing arrays with Python scalars) -...

Thanks for opening this issue @asmeurer. Agreed that 0-D arrays probably make the most sense here. As we've already departed from NumPy behavior for reductions (e.g., `sum` et al returning...

@rgommers Before moving forward with this PR, we need to ensure buy-in from PyTorch. The current proposal deviates from supported PyTorch [behavior](https://pytorch.org/docs/stable/generated/torch.take.html) in the following ways: 1. PyTorch does not...

DLPack support was removed from the specification for `asarray` in https://github.com/data-apis/array-api/pull/301. Concerns are still applicable for the buffer protocol and its support for "readonly". However, it would not seem that...

@leofang Agreed. I don't think there is any appetite for requiring implementations to display a warning (ala NumPy).

@rgommers I'll do a final pass through. Everything should be more or less complete. I can merge after.