Make Exponentional Backoff thread safe

[stephnr]

I saw an issue recently about how your Exponential Backoff function was not thread safe. I decided to implement this myself and would kindly like your criticism on it. 😊

[stephnr]

@jon-whit I believe this will solve your request.

[coveralls]

Coverage increased (+0.6%) to 84.492% when pulling 4036378 on defaltd:master into 62661b4 on cenkalti:master.

[cenkalti]

I am sorry I will reject this. I don't want to put a mutex into the struct. If you need thread-safe access to backoff instance, you have to solve it outside this library.

[stephnr]

Is there any reason why? Do you envision this to have performance issues or something?

[cenkalti]

I don't want to complicate the library.
What's your use case? Why do you need thread-safety from this library?

[stephnr]

No specific use case here. Just wanted to help out with a previously logged issue. That is all.

…

On Sun, Oct 7, 2018 at 10:27 PM Cenk Altı ***@***.***> wrote: I don't want to complicate the library. What's your use case? Why do you need thread-safety from this library? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#66 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE4V5323ZwyTsC95NaveddoMoehoA0IIks5uimPFgaJpZM4XL8s0> .