Johan Mabille

We sould probably release xtensor 0.25 first, since no release of xstensor with the upgrade to xsimd 11 has been done yet.

xtensor provides an API similar to numpy, where `reshape` changes the shape of the passed array. xtensor is missing a free funcion `reshape`, but if we add it, it should...

> I might be wrong but AFAIK, xarray doesn't store any information related to the rank of the array but Fortran specifies rank of the > array in its type...

> Basically the return type depends on the size of shape argument. If shape is of size n then returned xt::xtensor would be of rank n Ha I see; indeed...

@certik That's it. This limitation on `xtensor::reshape` is because it operates in place, like in NumPy. I think we don't want to mix "copy" and "in-place" behaviors in the same...

Actually the default container for `xtensor` and `xarray` is not `std::vector`, but [uvector](https://github.com/xtensor-stack/xtensor/blob/69eaac532f4da1c010b179b7ac2f471693dd9f0f/include/xtensor/xstorage.hpp#L42), which does not preserve its elements when resized. Anyway, the resize with preserving should be independent from...

I guess we need to capture `needs_cast` [here](https://github.com/xtensor-stack/xtensor/blob/master/include/xtensor/xassign.hpp#L1220), but I wonder if it's a compiler issue. Do you have the same issue with MSVC 2022 ?

We have a performance issue with the current implementation of the views, wihch produce bad assembly code. This issue is under investigation.

A way to cover most of the use cases from the bindings is to test: - with column-major order - with a tensor whose shape is a vector of signed...

> How would we ensure that all possible functions are included? I'm not sure that we can; but that should not be a blocker. Also I'm not sure we need...