-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added fixes for building with clang 19 #2821
Added fixes for building with clang 19 #2821
Conversation
Hey @JohanMabille, @SylvainCorlay can this move forward, or is anything blocking it? It would enable us to move to clang19 :) |
Just to note, the patch here is rather minimal, it just enables some ifdef-case that previously did not include clang 19. Maybe that helps the review? |
This would be great to get merged in, as OpenMC continues to have issues (exasmr/openmc#52) and (openmc-dev/openmc#3183) with LLVM 19 due to this. We can pass |
Can we please merge that ? This is starting to block us as well. |
bump 🙂 |
Hi everyone, Sorry for this very late reply and the inconvenience, I've been swamped with other tasks, but now I'm back on xtensor. I could not solve the conflicts on this PR (because I cannot push on the branch), so I opened a new PR that superseds this one (@vakokako like for your previous PR, I cherry-picked your commit so that you keep the credit for the fix). #2833 has been merged on top of backard incompatible changes that reorganizes the code (basically moving headers to dedicated folders, building with C++17 by default, and replacing backported features with their standard implementation). If you need this change in a backward copatible branch, let me know, I can backport it and quickly release a 0.25.1. |
@JohanMabille awesome, thanks! |
xtensor 0.26 has been released, it includes this fix. Notice that we have upgraded to C++17, and we plan to move to C++20 quickly. |
Fixes build issues with clang 19, discussed in #2783, #2804.