Tony Arcieri

@gaia to the extent this can be used as a digital notary service, I think the main idea here would be notarizing things as Cosmos transactions, which are validated and...

> Whether it will include full-optimized code, arch-agnostic vs arch-dependent, pure rust vs FFI, assembler allowed? The other crates in https://github.com/RustCrypto all provide a pure Rust portable implementation (written in...

Just wanted to note we have full scalar, field, and curve arithmetic support in both the `p256` and `k256` crates including point compression/decompression, the group operation (i.e. addition), as well...

@arnoldtonderaimarunda there's nothing specific to glibc in nio4r. This error relates to the version of glibc that nio4r is compiled against. If you compile a new version, it should link...

Unfortunately that doesn't really narrow it down very much, as that's where the bulk of libev's functionality is. There is definitely work needed on signal handling (see #134)

libev works on Windows via the select backend. It can’t handle a large number of I/O objects and performs poorly as compared to e.g. IOCP, but the base functionality should...

I agree that consistent signal handling behavior is desirable. The correct way to handle this in libev would be to wrap its own signal handling behavior: http://search.cpan.org/~mlehmann/EV-4.21/libev/ev.pod#ev_signal_-_signal_me_when_a_signal_gets_signalled! Handling forks is...

The tl;dr: of the libev advice is to install a fork handler (i.e. `pthread_atfork()`) which resets the signal mask. However this claims it isn't as simple as that: https://lwn.net/Articles/415684/ From...

You can certainly try to use it, although I'd definitely like to get the libev backend fixed.

@headius what you're describing makes sense, but how do you multiplex across multiple selectors?