Current warnings on M1 Mac about nio4r HOT 6 CLOSED

It's a bit tricky because the libev API for running code within the event loop and releasing the GVL are both callback-driven and therefore can't be composed easily, so it's necessary to patch releasing the GVL directly into the libev event loop.

There's a large comment describing the situation in the code.

from nio4r.

This is a common pattern for adding extra information to assertions, not sure what the solution is.

from nio4r.

@ioquatix Looks like a void cast is the solution on the intertubes. Can do them individually or use a macro:

#define m_assert(expr, msg) assert(( (void)(msg), (expr) ))

from nio4r.

Is this fixed upstream in libev? Because that would be the logical place to fix it.

from nio4r.

@ioquatix How do y'all pull in the libev code? Is it a submodule?

from nio4r.

No you have to copy it and manually move the changes. Normally I just replace the entire source tree and then manually revert the chunks of code we've changed. It's a little cumbersome.

from nio4r.