Mateusz Poliwczak
Mateusz Poliwczak
I think this proposal offers a performance advantage compared to #65562. The Read method on per-source RNGs can be optimized, whereas with #65562, `Rand.Read` would need to call each time...
@rsc With this approach it would be also nice to define some globals, like `CWD`. Zig also has a simmilar abstraction in the std, also called `Dir` https://ziglang.org/documentation/master/std/#std.fs.Dir.
Also ```go // Methods on Dir are safe to be used from multiple goroutines simultaneously. ``` Is this true for `Close`?
@rsc I think that there is a special `AT_FDCWD` fd for that. man openat(2): > If pathname is relative and dirfd is the special value AT_FDCWD, then pathname is interpreted...
@rsc Was this https://github.com/golang/go/issues/64802#issuecomment-2101504892 addressed? Is there a need for this GODEBUG?
From the output it is clear that the cgo resolver is being used, so out of our scope.
Can you try forcing the go resolver and see if it helps in your case? `GODEBUG=netdns=go`
`GODEBUG=netdns=go+2`
So the tittle is incorrect, it resolves correctly, but it fails to connect to the server when ipv6 is unavail, right?
@mknyszek If a new goroutine is desired for a finalizer it can always `go func`, so it might not be a huge issue.