Emil Dotchevski
Emil Dotchevski
I also hit this problem. I think it is not a good idea to change glad to use thread-local by default, just provide a macro that we can use to...
This is interesting, but maybe I'm missing part of the motivation for it. Would this approach not be sufficient for your use case: ``` leaf::try_catch( [] { return open_project ();...
I'll review tomorrow, but I have questions: 1. What happens if we make this change: ``` int r = leaf::try_handle_all( []() -> leaf::result { return leaf::new_error(info{}, info{}); }, [](info) {...
I'm concerned about making it even more difficult than it already is to know what handler will be called when. Without `handle_more`, at least we know we have to consider...
Try with the latest release please, let me know.
The support for `boost::exception_ptr` under `-fno-exceptions` is a new thing, though I didn't take a note in which Boost release it was introduced.
Nobody is actively developing Appler. It's not historically inaccurate to "merge the subpixels", it's just inefficient to do (Appler was originally developed on 12 MHz 286 and could run on...
I'm not an expert on coroutines but this will likely not work in general. The error objects in LEAF are stored in a `leaf::context` in the scope of `try_handle_all`/`try_handle_some`/`try_catch`. Before...
To support your use case, is it sufficient to `co_await` on the `try_block`? Would the static dispatch be based on the return type?
I think this will have to wait I need to do more research about coroutines before I commit to any support.