Francesco Casula

Same here with go 1.18 ``` fatal error: checkptr: pointer arithmetic result points to invalid allocation goroutine 619 [running]: runtime.throw({0x2bf0282?, 0x4a08f9?}) /usr/local/go/src/runtime/panic.go:992 +0x71 fp=0xc001876b68 sp=0xc001876b38 pc=0x469d71 runtime.checkptrArithmetic(0x0?, {0x0, 0x0, 0x0?})...

Sorry for jumping in but I've been working on other clients (Golang) and I'm trying to figure some things out myself. In regards to: > I guess, the requirement to...

> Just to remove potential confusion; this is only partially relevant for this topic. > Manual acknowledgement on the application side via calling acknowledge() in this client library is decoupled...

> Seems like the alg is off for the first second. Any idea on whats going on? Try with burst 1. https://github.com/go-redis/redis_rate/issues/58#issuecomment-821225658

> Why did you close this @fracasula? I needed more time to understand if I was reporting a false positive due to things like bad configuration. Compare these two benchmark...

> you will have to iterate till needed index, and then return early How do you return early though? Same for `ArrayEach`, how do I just get the first element...

> > you will have to iterate till needed index, and then return early > > How do you return early though? Same for `ArrayEach`, how do I just get...

Also, did you happen to do a quick benchmark to see what kind of improvement are we talking about?

Similar issue here, I have a main ActorContainer called TilesGrid with many Tiles (actors) inside. TilesGrid is biggest than canvas size, so I need a dragging functionality to offer an...

In my opinion this can be considered as a bug because, after the dragging operation, the new tiles are shown and **visible** (but aren't clickable/draggable). In the first screenshot you...