Jameson Nash

According to the suggestion there, this is a `Test.detect_unbound_args` bug, since it doesn't know to model the covariance implications of this definition

The `UndefVarError` is correct, as is the message about `detect_unbound_args` being supposed to be able to detect this, but just the `Test.detect_unbound_args` is failing to correctly detect it

Taking effectively unbounded time on badly designed code patterns is not a bug, unless you can show it is generating an ever growing list of candidates

Looks like a tmerge / lattice convergence issue with the constant Conditional (t isa Tuple resolves to `Core.Compiler.Conditional(slot=2, thentype=Tuple{Vararg{Int64}}, elsetype=Union{})` which is a refinement of `Const(true)`) interacting badly with the...

Since libuv is a multithreaded library, most documentation for `fork` will typically state that executing anything but execv is undefined behavior in the child process. There is some limited support...

To reiterate, the documentation for `fork` points out that even continuing to use libc is not safe: ``` * After a fork() in a multithreaded program, the child can safely...

The lack of annotation was an oversight. While used internally by libuv, any external library should also be using them to correctly access libuv (if needing to do similar conversions...

One idea might be to call `SetLastError` just before return (or callback) in libuv, so that the value is visible to the user application if it wants to retrieve it.

> On Windows the readdir equivalent (NtQueryDirectoryFile) already returns file attributes in the initial call, all the stat calls are superfluous. What `stat` calls? If you don't want to come...

It seems a bit awkward to add a new flag for this. In my applications (aka Julia), we just call `loop->stop_flag = 0` just before entering the loop (although doing...