On Tue, Jul 9, 2019 at 10:36 AM Daniel Eloff <dan.el...@gmail.com> wrote: >> >> >> 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.
And not only that, it's complicated. The language spec is not the right place to dig into the complexities of how to use select safely while avoiding race conditions. There is just too much to say. And there are no docs for select other than the language spec. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcXpADAzc_OJHCZYoXqyDGm%3DfuAYmvsjeMVsPCxv%3Dd68Eg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
