Performance and pointer vs non-pointer receivers

[petar]

Determine experimentally whether pointer or non-pointer receivers of generated types produce faster code.
Theoretically, it is unclear:

• Non-pointer receivers afford a single allocation for entire recursive user types. But they incur a stack allocation when MapIterator is called (although it is possible that Go optimizes this away.)
• Pointer receivers avoid the above problem, but then every level of a user type involves allocations.

For comparison, note that Protocol Buffers have opted for pointer receivers.