I believe the question was about the specific implementation of noescape, specifically the "exclusive or" in that unsafe expression.
To the original poster: are you just curious why, or is there a more specific question you have? I'm assuming that function looks like that to correctly trick the compiler; perhaps escape analysis gives up if you start xor-ing uintptr values or something like that. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/2f2b4f8d-1218-4a12-adf1-34e8b4d63648%40googlegroups.com.
