tree f1e96f07266ff042a5c943576f35ee9c13aa7760
parent 00998c7dd9d789e353c9518d13864b75cd23c55d
author Joe Tsai <joetsai@digital-static.net> 1589486380 -0700
committer GitHub <noreply@github.com> 1589486380 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJevaMsCRBK7hj4Ov3rIwAAdHIIAFN42TaaB0xzhjEhJ4qJ3Nyq
 C0rPzHBlG+N93Y0mKryYZohjflK3bHHddkRhgGUq8gdFiKayd2LnSSRPWADDH5s6
 c6KWjxjxY7pbLQHYKJ7OM5PNqJXylmdouq4MVlJ2shb5fHUu1OzA9k0e3R+1pz2J
 jZIoq0IsbxvrUDJKoG3h+ark4qZarAX8OGNbSzD7WMnoExIaa9IG9cPaOJmtQHXv
 qjXA7cKnh/GnlFHaBHEgzD6Yu5hW4zFsJV/nCRWOIAI+I7WAHoDNGTMRjMAh1Lmc
 oH9XlRkGbZI8znwSyMSjnmCjTZFbuN840akagekWgA5bzU/yXMYorh0Ke5kO5eE=
 =fM5D
 -----END PGP SIGNATURE-----
 

proto: make InternalMessageInfo functional (#1129)

The InternalMessageInfo type only exists to implement the
XXX methods on generated messages where those methods were
only ever intended to be called by this module itself.

Since v1.4.0, this module no longer relies on the XXX methods,
so the InternalMessageInfo and its implementation is supposed
to be dead code. Unfortunately, there are external usages that
violate our compatibility agreement and either directly call
the XXX methods or indirectly call it because some library
type-asserts to the existence of these methods.

This change adds minimal support for InternalMessageInfo by
just calling out directly to the v2 implementation.