On Tue, Sep 18, 2018 at 2:04 PM, Eric Raymond <e...@thyrsus.com> wrote: > On Tuesday, September 18, 2018 at 4:10:52 PM UTC-4, Ian Lance Taylor wrote: >> >> Signals in Go never interrupt functions. > > > Thank you, that was an admirably clear reply. > > I think this needs to be documented more prominently. Can I file an MR > against the Go documentation? Web search is not telling me where that > repository is. I understand it nmay be privare. > > If you would prefer, I can open a documentation issue on it.
Sure. The docs for the os/signal package are in src/os/signal/doc.go. There isn't a separate Go documentation repo, unless you count the blog which is at go.googlesource.com/blog. > Under "Default behavior of signals in Go programs" in the Signals package > documentation, the one sentence "Defer hooks are *not* fired after signal > receipt." would head off potential confusion on this issue. Well, maybe. I agree that that would help if you come with a certain vision of how signals work. But I don't know how many people come in with that vision. Maybe we should start by saying something like "signals do not interrupt the execution of Go programs." Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
