@diddledan huh, well that's not what I expected. Why does the pointer change?
Some sort of reallocation? Recursion greater than 64 frames seems to cause it to reallocate memory space.
This actually seems sane since go does not want you to do pointer arithmetic. Though you can use unsafe package.
@diddledan annnnd I missed the twitter link and basically rehashed everything everyone already said!
stack grows and moves, pointers get updated automatically.
This would be bad times if you used unsafe. Everywhere else, perfectly normal and sane.
This server was setup for the Ubuntu community to use.