Is encoder thread-safe?

[Juncheng Yang]

Can I use the same encoder in multiple goroutines?

[Darren Li]

The core struct (type reedSolomon struct) is largely stateless, except for the field tree of type inversionTree, which is a specialised cache for temporary storage of matrices used for reconstruction.

inversionTree is protected by a mutex.

So to the best of my knowledge, yes it is safe to use it in multiple goroutines for all scenarios.

[Juncheng Yang]

Thank you, Darren! I will update here if it is not.

…

On Mar 3, 2019, 01:11 -0500, Darren ***@***.***>, wrote: The core struct (type reedSolomon struct) is largely stateless, except for the field tree of type inversionTree, which is a specialised cache for temporary storage of matrices used for reconstruction. inversionTree is protected by a mutex. So to the best of my knowledge, yes it is safe to use it in multiple goroutines for all scenarios. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Darren Li]

All good.

The same architecture is implemented in a Rust port of this library, and Rust would complain if it's not thread-safe when you use it in a multi-thread scenario. So overall I believe it is thread-safe.

[Klaus Post]

Yes, it is, but checking with the race detector is of course always recommended - if nothing more then to check your side of the code.