Athan

Another possibility would be adding a functional API for resolving the number of bytes, with some consideration for lazy arrays and arrays having non-deterministic shapes.

**Update**: I've added a note similar to what's suggested for `cumulative_sum` in https://github.com/data-apis/array-api/pull/851.

As this PR has not received any objections since April 18, is consistent with `cumulative_sum`, and has been previously discussed during workgroup meeting, I'll go ahead and merge. Any further...

@honno Were you able to triage the Dask issues with the test suite?

@honno Is there anything more that we need to do with this PR?

> Does it make better sense? Yes, I think so. Based on the discussion above, my conclusion is that we should add some language to a section in "Design topics...

Given the ambiguity of supporting a tuple of axes in `expand_dims`, I wonder if there is room for an alternative API which avoids the ambiguity altogether. Namely, ```python def spread_dims(x:...

Thanks, @NeilGirdhar, for opening this issue. This might be another candidate for a "deep learning" extension (ref: https://github.com/data-apis/array-api/issues/158). Both PyTorch and Jax, which have similar APIs, place it in their...

@Pranavchiku Indeed, Boost makes heavy use to templating which can be hard to grok. With practice. :)

@Planeshifter Sorry, I have already forgotten. Can our existing automation work with conventional commits? Or do we need to include additional meta information in the commit messages?