Tom Nicholas

> my point about the bins is that if the inputs are two xr.datasets, then also the bins should be two xr.datasets. This makes sense, but it sounds like this...

Okay great, thanks for the patient explanation @aaronspring ! Will tag you when this has progressed to the point that you can try it out.

> We may want to also reimplement it using numpy_groupies, which I think is smarter than our implementation in xhistogram. Given the performance I found in https://github.com/xgcm/xhistogram/issues/60, I think we...

## Q: Use xhistogram approach or flox-powered approach? @dcherian recently showed how his [flox package](https://github.com/xarray-contrib/flox) can perform histograms as groupby-like reductions. This begs the question of which approach would be...

> Could you show the example that's this slow, @TomNicholas ? So I can play around with it too. I think I just timed the difference in the (unweighted) "real"...

> it was triggering a load Can we not just test the in-memory performance by `.load()`-ing first? Then worry about dask performance? That's what I was vaguely getting at in...

Thank you for starting this discussion @lucascolley, and thanks for tagging me! > function `materialize(x: Array)` Note that the signature here should probably be more like `materialize(*arrs: Array, **kwargs)`, as...

These failing tests from the CI do not fail when I run them locally, which is interesting. ```python FAILED xarray/tests/test_backends.py::TestH5NetCDFViaDaskData::test_outer_indexing_reversed - ValueError: dimensions ('t', 'y', 'x') must have the same...

Notes to self: - [ ] Try to consolidate indexing tests with those in `test_variable.py`, potentially by defining a subclass of Variable that only implements async methods - [x] Use...

The changes needed in zarr-python have just been merged upstream (but not yet released).