reflect: use runtime's memmove instead of its own
They will both need write barriers at some point. But until then, no reason why we shouldn't share. LGTM=rsc R=golang-codereviews, rsc CC=golang-codereviews https://golang.org/cl/141330043
Showing
Please
register
or
sign in
to comment