The second possibility you described is exactly what I’m worried about. But I have several places where I’m doing something like b.data[b.grow()] = bt and wouldn’t want to break that up into two lines everywhere. I was wondering if you could find anything else in the spec to guarantee that the index (b.grow()) is evaluated first, before the slice is identified.
-- 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.
