Alan Somers
Alan Somers
What error do you get when using `#[automock]`? I suspect that you'll have to add a `: 'static` bound to `T`.
Those errors are saying that you need to add a lifetime parameter to the references in your function arguments. The easiest one to add is `'static`. Can you do that?
Testing aarch64-freebsd in CI would require usermode qemu emulation. It's possible, but it would take some effort to setup.
Oh, there's a new option now. Cirrus CI can do CI testing on arm64. Currently they only do it for Linux, but it would be easy to add FreeBSD, if...
This is probably a bug in your application. `select` can only be used with file descriptors up to `FD_SETSIZE`.
No need. libc's exported `FD_SET` is already safe. That's why the application panic()ed rather than segfaulted.
> Just for clarification, the functions prefixed with `FD_` are for file descriptors? What about `CMSG_`? The `CMSG_` functions are not related. They are intended for use with sendmsg(2) and...
Some of the other types haven't been changed yet, though.
You're right that `fork` is unsafe. But is it `unsafe` in the Rust sense? I think we should follow whatever decision rust-lang makes in the issue you linked.
Is there any undefined behavior associated with calling async-signal-unsafe functions after forking? I can't find any. [fork(2)](http://pubs.opengroup.org/onlinepubs/9699919799/) doesn't mention any undefined behavior. Instead, it suggests not calling async-signal-unsafe functions in...