+mpvl although my instinct is that this is all working as intended, and types are not goroutine-safe unless they explicitly say so.
On Tue, Jun 21, 2016 at 2:33 PM, Ian Lance Taylor <i...@golang.org> wrote: > On Mon, Jun 20, 2016 at 9:15 PM, <alke...@gmail.com> wrote: >> I am guessing the same efficiency should be possible. Except, each call to a >> chained Transform >> would involve a couple of allocations (to create the state). On the good >> side, this simplifies concurrent >> code sharing the same object (no locks), avoids the original problem >> (concurrency corruption) and avoid >> having to create multiple instances of the same chain if one is to avoid >> locks (saves allocations here). > > Unfortunately, a couple of allocations is not the same efficiency. > > That said, this is mpvl's code and he would make the final decision. -- 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.
