-
Notifications
You must be signed in to change notification settings - Fork 38
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
no make_unexpected with nsel_USES_STD_EXPECTED #66
Comments
Thanks for the heads-up. Function Consequently The idea of excpected-lite being a migration path to I'll look into that, unsure how quickly I'll get at it. |
Thanks for looking into it. The challenge here lies in the expected-lite being used by other libraries taking the liberty in using the P0323R suggested feature throughout their codebase. My suggestion is merely a quick-fix, trying to forward the ´std::unexpected{}´-idiom to the ´make_unexpected´ functionality. |
I'll add Have yet to correct the test suite for use with |
Argh, I now realise it's (also) about Will continue tomorrow. |
@martinmoene Thanks for tackeling the issue. I'll try to the current head in my scenario and advise the authors of BehaviorTree.CPP to use a new release, as soon as available. |
Currently adapting the test suite for when Will make a release after that, presumably v0.8.0. |
Just tested compliation with gcc and clang locally, looks good, so the issue can be closed, |
Thanks for your feedback & you're welcome. |
I'm using the library indirectly via BehaviorTree.CPP.
Using a recent clang(17.0.3)/gcc(14.1) the code doesn't compile anymore due to make_unexpected not being available.
I currently patched this locally by adding this into the
#if nsel_USES_STD_EXPECTED
path (~ line 253):If wanted, I can submit a PR with the change or maybe I'm doing something wrong here?
The text was updated successfully, but these errors were encountered: