Maik Nijhuis
Maik Nijhuis
This PR partially addresses #2707. When using XSimd, the following code will compile, however, the resulting code is inefficient if the return type of `operator|(const char&, const char&)` is `int`...
The following simple test code does not compile when using -DXTENSOR_USE_XSIMD: ``` #include void xtensor_or(xt::xtensor_fixed& b1, const xt::xtensor_fixed& b2) { b1 = b1 | b2; } ``` The compiler complains...
When using xt::where with xtensor types that have complex values, GCC gives this error: `no matching function for call to ‘select(const bool&, const std::complex&, const std::complex&)’`. The error occurs since...
When opening a file read-only on a "dvs" filesystem, HDF5 will complain that it cannot lock the file and it reports (among others): #006: H5Fint.c line 1898 in H5F_open(): unable...
GCC 13 may give warnings like: ``` /home/maik/scratch/schaap/everybeam/include/xtensor/xutils.hpp:33:6: error: "_MSC_VER" is not defined, evaluates to 0 [-Werror=undef] 33 | #if (_MSC_VER >= 1910) | ^~~~~~~~ In file included from /home/maik/scratch/schaap/everybeam/include/xtensor/xcontainer.hpp:25,...