go-baseutils VS queue

Best practices for channel in concurrency, including fan_in,fan_out,map_reduce,or_done,orderly,pipeline,stream,generic version can be found at https://github.com/songzhibin97/go-baseutils/tree/main/app/bconcurrent

Cache-related components > buffer & mbuffer provide similar functionality, buffer has more encapsulation and implements some of the io interfaces, while mbuffer is just a memory cache. > local_cache provides a local data cache, and also has some expiry mechanisms, you can set the expiry time, and regularly clean up the expired data, but he is now older, if needed there is a generic version https://github.com/songzhibin97/go-baseutils/blob/main/ app/bcache > singleflight wraps golang.org/x/sync/singleflight to prevent the impact of changes

i’m using these checks for my projects and I feel that this is more than enough: https://github.com/adrianbrad/queue/tree/main/.github/workflows

I plan to release a package that is supposed to provide multiple generic Queue implementations and it also defines a Queue interface that all implementations must satisfy. Currently, there are 2 implementations, a Blocking queue, and a Priority queue.

Hello again, I came up with this implementation that uses buffered channels: https://github.com/adrianbrad/queue/blob/blocking-channel-implementation/blocking2.go. In order to drain the channel during a Reset, the channel is closed and refilled elements, while Take listens for both new values and the close signal. What do you think? The original Reset implementation is a bit faster, you can check the benchmarks here: https://github.com/adrianbrad/queue/blob/blocking-channel-implementation/blocking_bench_test.go