-
Notifications
You must be signed in to change notification settings - Fork 92
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
Exception free error handling #49
Comments
Yes, I agree. |
What do you think this would look like, ideally? Would you use a lot of std::variant return types? Or std::expected? |
I actually like std::expected but its C++23 which is really std:: variant underneath. Maybe we can fallback to https://github.com/TartanLlama/expected |
Yeah, std::expected would be ideal. hffix currently has two properties which I like to preserve, if possible:
But maybe it's time to start relaxing these requirements. May I ask, what is your build environment? You have C++23 but you don't have exceptions? |
we can keep both of the requirements by bundling the above library in the source code. it's header only so i don't expect any issues. I have C++20 with exception disabled because of hard latency requirements. |
I second the requirement from alfred-666. I am in a cpp17 env so cannot use std::expected. I'm aware of the expected in github by Sy Brand but agree with you that it is undesirable to have a blatent dependency on that by hffix. Perhaps bundling is the answer there but I am not sure. This thread is quite old, are there any plans to address the issue please? |
Some environments don't have luxury of exception so having exception free code paths would be great
The text was updated successfully, but these errors were encountered: