Closed burnpanck closed 4 years ago
Sorry, my fault - there is no resolution to that linked issue at all - I was still seeing my own local solution. Let me propose a resolution to both then...
Can you try latest Outcome on your system please? Define the SYSTEM_ERROR2_NOT_POSIX
macro before usage of Outcome.Experimental, in theory it should now no longer do anything requiring POSIX. If it does, let me know what.
Closing due to lack of timely response.
I can now confirm that the current master
branch as of today (which includes this fix) does work in my setup, which is non-posix, non-windows. Sorry for the late answer.
This is a follow-up to your recent fix to status-code issue 18 (thanks by the way!): Now that status-code doesn't try to provide
posix_code
anymore, outcome shouldn't expect to find it unconditionally.