keep94

optiopay/kafka to use exponential backoff on nodes that are down

1

Background: The KAFKA that I have to write to has 5 nodes, one of which is permanently down. I write to the nodes round robin style. Every 5th write fails...

I notice that List[T] and Map[T] use by-reference semantics whereas Set[T] uses by-value semantics. I propose that all the main immutable types in this package use by-value semantics like Set[T]...

Another release?

7

Would it be possible to do another release? 1.8.0 was done two years ago. We would like a release that includes this change here: https://github.com/lz4/lz4-java/commit/1f2f4d333eaf8d95eea34b0b80a7d56e3458b911 as we want to be...

big.Int instances are mutable. Which means that if a caller calls math.MaxBigInt(a, b) and later changes a or b, then what math.MaxBigInt returned could change unexpectedly Consider the following code...

I am very impressed with the simplicity of your consumer API. Have you considered adding a producer API too?

I tried using the -hide-private-members option. This option hides all the private members of each struct or interface, but I still see all the private (unexported) structs without their private...

It would be really cool if the immutable collection types include an All() method that returns a golang iterator over all the elements in that collection.