> > > In my opinion the best place for this kind of discussion is a blog > post or talk. >
I disagree strongly. If there's a mode of operation that's dangerous when I'm operating a car or machinery I want it to not just be called out in the manual, but called attention to in a big bold font. Likewise with software engineering if there's a dangerous edge case it should be called out right there in the official documentation. This goes double for situations like this where the behavior is surprising or not intuitive. The number of replies to this thread with people suggesting broken workarounds due to race conditions between sending and timeout, suggests not only that this behavior is not intuitive, but it's also extremely fraught. The great thing is Go is open-source so I'll just create a commit with what I feel is the appropriate change to the documentation, and submit it for review. Cheers, Dan -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/db8874f2-ecfa-42fa-a46a-c28b811d6fa9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
