Update xtensor

[fbourgin]

Hi, as xtensor-python, xtensor-r needs to be updated after xtensor-stack/xtensor#2829.

[JohanMabille]

Thanks for opening this one! I'll fix the CI in a dedicated PR so that you can rebase yours.

[JohanMabille]

The CI has been fixed, you can now rebase your PR. I've removed the environement-dev-win.yml file because it was to used anywhere.

[fbourgin]

Thanks! It seems to work now, but I had to upgrade Xtensor.R in a fork. I opened a pull request for that fix in xtensor-stack/Xtensor.R#39.
Should that PR also include the upgrade to xtensor 0.27 and C++20, or would you prefer that in a separate PR?

[JohanMabille]

Thanks! It seems to work now, but I had to upgrade Xtensor.R in a fork.

Thanks for doing it. I'm going to fix the CI there so that we can merge your PR, and then merge this one. Thanks again for your patience!

Should that PR also include the upgrade to xtensor 0.27 and C++20, or would you prefer that in a separate PR?

I think it should be done in a dedicated PR. This way we can release xtensor-r compatible with xtensor 0.26 before upgrading to xtensor 0.27

[fbourgin]

Thanks for fixing the CI in Xtensor.R!
If xtensor-stack/Xtensor.R#39 looks good to you, I think it's ready to be merged.
I also have a separate PR ready for the xtensor 0.27 update.

[JohanMabille]

Apparently Xtensor.R needs additional fixes (and I noticed that the xtensor packages were removed from CRAN, that should be investigated and fixed somehow), but I don't want to block this PR longer. So let's use your fork of Xtensor.R here until everything is fixed upstream.

[JohanMabille]

Unless you have additional changes to push, feel free to mark this one as Ready for review so that I can merge it and tag a release of xtensor-r.

[fbourgin]

Yes, it appears that xtensor-stack/Xtensor.R#39 is currently failing in CI due to a dependency on xtensor-r.
I can try to fix that after the update to xtensor-r is complete.
I believe this PR is now ready to be merged.

[fbourgin]

Apparently Xtensor.R needs additional fixes (and I noticed that the xtensor packages were removed from CRAN, that should be investigated and fixed somehow), but I don't want to block this PR longer. So let's use your fork of Xtensor.R here until everything is fixed upstream.

CRAN submission can certainly be challenging when dealing with complex workflows. You might be interested in R-Universe (https://r-universe.dev/search). We use it ourselves for the evalhyd R package, which is based on xtensor (https://hydrogr.r-universe.dev/evalhyd).

[JohanMabille]

Thanks again for your work on this and your patience!