No Go type should be assumed to be safe for concurrent use unless explicitly documented otherwise (or obviously safe, for some definition of "obvious"). On 13 Jun 2016 17:14, "Sam Whited" <s...@samwhited.com> wrote:
> On Mon, Jun 13, 2016 at 3:16 AM, <m...@golang.org> wrote: > > A single collator instance is NOT safe for concurrent use. The buffers > are > > only used to store the keys, but a Collator has some scratch buffers that > > are used to avoid allocation. > > Maybe the documentation could state this explicitly? I think I > probably would have assumed that Collator's were concurrency-safe too. > > Best, > Sam > > > > -- > Sam Whited > pub 4096R/54083AE104EA7AD3 > https://blog.samwhited.com > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
