> Is this simply a recommendation or should the docs be updated to clarify what > this means?
perhaps the latter, although that question only seems to come up once every two or so years. here's a good link: https://groups.google.com/d/msg/golang-nuts/XqW1qcuZgKg/Ui3nQkeLV80J the entire discussion where i found it is interesting: https://groups.google.com/g/golang-nuts/c/vN5ncBdtkcA/m/zf6EydsFsxgJ On Mon, Sep 21, 2020 at 4:15 AM Henrik Johansson <dahankz...@gmail.com> wrote: > > > https://golang.org/pkg/sync/#RWMutex > > Holds that this prohibits recursive read locks but why would it? > I understand that deadlocks can happen in case write locks are held in > between the read locks > but why can't a goroutine issue several RLock calls? > > It does actually work in the playground. https://play.golang.org/p/nOehJaeikxA > Is this simply a recommendation or should the docs be updated to clarify what > this means? > > > -- > 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/CAKOF696YKSGn3j%2BcyX7o0ukA7wnD2Kq19_QGefUoeMELUZGOWA%40mail.gmail.com. -- 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/CAK4xykUmZK0HB1f84uc%2BXATMZRcuZ6nJr-ri5QaBWQnAS_r1iQ%40mail.gmail.com.
