Oleg Kovalov

Hi, sorry for the problem and thanks for the detailed description. I will take a look shortly.

Hi, sounds useful. Any idea for the api? Currently we have Walk method to iterate over all fields. Probably it should be replaced with something userfriendly or...I don't know.

Good catch, thanks!

Probably this was the reason :) https://github.com/allegro/bigcache/actions/runs/6145556141/job/16673759956?pr=374#step:5:25

AFAIR it's because during a test run `os.Stdout` is replaced with a test-specific writer to catch the full output. And because this we're logging in a goroutine we can log...

By "skipping" you mean that you don't see function names and only colourful squares? Why not to click on them to expand them?

LGTM

> it is also need to be defined is it better to have "maximum wins" or "first wins" approach? seems like "maximum" wins is better with fallback to "first wins"...

Thank for comments, guys. Issue isn't written in a stone. So we're free to decide what do we want 😉

Ruleguard, probably? @quasilyte