On Thu, Apr 21, 2022 at 7:16 AM 'Bryan C. Mills' via golang-nuts
wrote:
>
> Even ENFILE and EMFILE are not necessarily blindly retriable: if the process
> has run out of files, it may be because they have leaked (for example, they
> may be reachable from deadlocked goroutines).
> If that is the
On Wed, Apr 20, 2022 at 6:46 PM 'Damien Neil' via golang-nuts
wrote:
>
> The reason for deprecating Temporary is that the set of "temporary" errors
> was extremely ill-defined. The initial issue for https://go.dev/issue/45729
> discusses the de facto definition of Temporary and the confusion
Even ENFILE and EMFILE are not necessarily blindly retriable: if the
process has run out of files, it may be because they have leaked (for
example, they may be reachable from deadlocked goroutines).
If that is the case, it is arguably better for the program to fail with a
useful error than to
On Wed, Apr 20, 2022 at 6:46 PM 'Damien Neil' via golang-nuts
wrote:
>
> The reason for deprecating Temporary is that the set of "temporary" errors
> was extremely ill-defined. The initial issue for https://go.dev/issue/45729
> discusses the de facto definition of Temporary and the confusion
The reason for deprecating Temporary is that the set of "temporary" errors
was extremely ill-defined. The initial issue for https://go.dev/issue/45729
discusses the de facto definition of Temporary and the confusion resulting
from it.
Perhaps there's a useful definition of temporary or
