Please see the code snippet, is the behavior of copy correct?
From the document I just saw overlapping is allowed but doesn't describe
the expected result. From what real program, it seems the behavior is
similar to memmove().
As I understand memmove() does more bookkeeping hence the performance is
worse than memcpy(). Say if I have a lot of memory to copy and want to
squeeze the performance (also in my program I prefer memcpy behavior, if
it's consistent at all) is there any why in Go that I can do better than
BTW, where can I find the copy builtin implementation in the go source
tree? the cmd/gc/builtin.c doesn't seem to have it.
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 firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.