Add generator option to always produce pointer receivers

[mjmar01]

I'd like to propose a command line parameter for the generator like "receiver-preference" or similar to modify the receiver logic for Marshal and MsgSize methods. So it could either do:

• Pointer receivers for everything
• Pointer receivers for unmarshal methods, but non-pointer receivers for marshal methods (this might also satisfy a previous issue)
• Dynamic like before

Currently the generator will frequently mix receiver types for generated methods. This causes annoyances in some scenarios like for example when using both the Unmarshaler and Marshaler interfaces in another custom interface. Since generated types often don't implement both of these interfaces at once, the custom interface might also become unusable.

Currently you could work around this by including unexported and omitted fields in the struct to fool the generator into using pointer receivers:

//go:generate msgp -unexported

type MyCustomType struct {
	forcePtrRcvr     struct{}    `msg:"_,omitempty"`
	ArbitraryField   int
}

But this is unclean and doesn't work when encoding to tuples using //msgp:tuple MyCustomType, when using basic types (not structs) or when unexported fields should not be serialized at all.

Let me know what you think and if I can provide further information or assistance :)

[klauspost]

If implemented as directives, I for sure wouldn't mind it. Keeping the commandline "clean" is IMO better design.

To me the cleanest would be:

//msgp:pointer

... simply as a file level directive.

[klauspost]

type NamedBool    bool

Will need some special care, as forcing pointers on these means the code will also need to change.

Also we maybe have to deal with the fact that the receiver can now be nil.

[klauspost]

See #357