Good question, I'm not much of a mobile developer so hopefully someone with
more experience there can chime in. But my thought would be that if you're
on mobile and need the performance of lite protos then you would probably
want to just read and write Any fields manually instead of using the helper
methods that require non-lite. If the extra boilerplate turns out to be
excessive, we could look into ways of updating the Any API to make it a
little easier to use with lite protos.

On Fri, Oct 7, 2016 at 10:15 AM, Tim Kientzle <> wrote:

> On Oct 7, 2016, at 9:54 AM, 'Adam Cozzette' via Protocol Buffers <
>> wrote:
> Here's the thing, though: we are actually thinking about removing the
> MessageLite::GetTypeName method at some point in the future. Lite protos
> are intended primarily for mobile and so in that environment it's important
> to keep the binary as small as possible and also avoid including symbols in
> the code that's distributed, whereas currently that method requires us to
> generate code that includes the message type names. So I think it would be
> best to avoid creating another dependency on that GetTypeName() method when
> it might be going away in the future.
> This seems to suggest that you don’t intend to support Any for mobile?
> Tim

You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to