i am obviously oblivious to what 'is in front of', but knowing that now [what light weight exceptions entails], I concur with you. As I noted in that same post, I 'get' [in respect of LEAF] the use-case of a c-api error-handler (but there must be plenty of those, no?), but otherwise I don't see it. From my personal perspective, I would not hesitate one second to use Outcome now, instead of any other solution better, or worse, just because it is going to be in some shape or form, but very similar, in the future standard.

The kind of code I write (the application areas) almost always demands logical correctness and other than the mythical OOM, no exceptions can occur (bar a bit of IO, which would live somewhere separately), so I have no need for any of these libraries, Most of my testing is fuzzing, let the computer search for bugs, not me or the user. Here I obviously actively use exceptions to figure out what happened if something does happen, it's easier than logging and builtin.

degski