The assembly should never write to a position / update the len beyond the backing array (specifically, the assembly is generated from code where the 'max stack depth' has been computed and validated, and the capacity of the slice is that size).
On Friday, March 22, 2019 at 5:39:36 AM UTC-7, Howard C. Shaw III wrote: > > On Friday, March 22, 2019 at 12:27:37 AM UTC-5, Tom wrote: >> >> The allocation is in go, and assembly never modifies the size of the >> backing array. Assembly only ever modifies len, which is the len of the >> slice and not the backing array. >> >> > Can the assembly ever modify len to a size greater than the length of the > backing array? When that happens within go, a new, larger array gets > allocated and the backing array gets copied to it. If it happens in your > assembly? > > Howard > -- 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.
