You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UV_PROCESS_DETACHED - how else do you fork off a daemon?
Note that this doesn't just apply to libuv, but also to libnative. The unix libnative versions are probably straightforward (just take a look at the libuv implementation).
Marking as E-mentor (I'll mentor)
The text was updated successfully, but these errors were encountered:
Fixed FP in `redundant_closure_call` when closures are passed to macros
There are cases where the closure call is needed in some macros, this in particular occurs when the closure has parameters. To handle this case, we allow the lint when there are no parameters in the closure, or the closure is outside a macro invocation.
fixes: rust-lang#11274rust-lang#1553
changelog: FP: [`redundant_closure_call`] when closures with parameters are passed in macros.
Some missing bits I just discovered:
UV_PROCESS_SETUID
- someone's gonna want thisUV_PROCESS_SETGID
- someone's gonna want thisUV_PROCESS_DETACHED
- how else do you fork off a daemon?Note that this doesn't just apply to libuv, but also to libnative. The unix libnative versions are probably straightforward (just take a look at the libuv implementation).
Marking as E-mentor (I'll mentor)
The text was updated successfully, but these errors were encountered: