That looks like a bug. I'd suggest submitting an issue. I think the check at the beginning of WaitN should just be removed, as the burst limit will be accounted for in reserveN later.
On Tue, Aug 23, 2016 at 6:32 AM Manlio Perillo <manlio.peri...@gmail.com> wrote: > Il giorno martedì 23 agosto 2016 12:03:37 UTC+2, Sokolov Yura ha scritto: >> >> What is rate.Limiter ? > > > golang.org/x/time/rate > > > Manlio > > -- > 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. > -- 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.
