Call Reset before UnmarshallVT to keep the default grpc semantic

[aureliar8]

Fixes #128

Contrary to what was discussed in the issue, I was not able to call ResetVT() before UnmarshallVT() because the reset method isn't always generated (it's only generated when the pool option is enabled)

Perhaps the ResetVT() method should also be generated when the unmarshal feature is enabled ?

[bhollis]

You should do the same trick as the code does to detect the MarshalVT method - use an interface that declares ResetVT and see if the type implements that interface. That way you don't have to depend on protobuf.

[fenollp]

In addition to @bhollis's comment I'd suggest to extract ResetVT generation from pool under a new option reset.

[fenollp]

Suggested change

	vv, ok := v.(reseter)
	vv, ok := v.(interface { ResetVT() })

[aureliar8]

I can't require the message to implement ResetVT() because this method isn't generated by default (it requires the pool option)
Doing so would break the codec for user who just use the marshal and umarshal features

But I can follow this style and do

Suggested change

	vv, ok := v.(reseter)
	vv, ok := v.(interface{ Reset() })

[fenollp]

You're right :) IMO the resetvt func should be turned into a plug-in that's activated automatically with pool plugin.

[aureliar8]

Don't you mean that ResetVT() should be generated automatically when the unmarshal plugin is enabled ?