* commit '538abc5b6514460fce1e72da9f49591c6d4ba2e0':
  Don't serialize required fields whose 'has' flags are unset.

* commit 'd6aeae143cde31b79a2d57a3ee0e41d9083d232d':
  Don't serialize required fields whose 'has' flags are unset.

Change-Id: Ibbe944fff83e44a8f2206e18ee9ec6f10661297a

* commit 'a896c1d8699a3a14aae94b7067339ebc5cccc794':
  Fix MessageNanoPrinter for accessors

* commit 'e7741c064ee4cdc5fa41e6444ed45131672fed97':
  Fix MessageNanoPrinter for accessors

accessors mode switches proto fields away from being public fields (which is
how MessageNanoPrinter found which fields to print via reflection). Add a
pass through the methods looking for generated accessor methods to print
those as well.

Change-Id: I7c47853ecbd5534086f44b25a89dbbe56f63ed03

* commit '6b9d96b2a3b32c141e2b105fcfde4f4b0dfae3f5':
  Avoid class initializers to help ProGuard.

* commit '3f9bd9989c79db575b83e2f96b48c695f30ca153':
  Avoid class initializers to help ProGuard.

Class initializers prevent ProGuard from inlining any methods
because it thinks the class initializer may have side effects.
This is true for static methods, but instance methods can still
be inlined, because to have an instance you will have touched
the class and any class initializers would have run. But
ProGuard only starts inlining instance methods of classes with
class initializers from v4.11b6, and Android uses v4.4 now.

This change tries to avoid the class initializers as much as
possible, by delaying the initialization of the empty array and
some fields' saved defaults until when they're needed. However,
if the message hosts any extensions, they must be public static
final and therefore introducing the class initializer. In that
case we won't bother with lazy initialization.

Change-Id: I00d8296f6eb0023112b93ee135cdb28dbd52b0b8

* commit '6a6b3b384c6084b3ce0de360b6dcb74a82bc23bb':
  Nano: don't generate accessor methods for nested methods

* commit 'cea499acf68b35921b956785c26c0e6f18c241c1':
  Nano: don't generate accessor methods for nested methods

For nested message objects, don't generate accessor methods because they have
a default value that is not a valid value (null), so there is no reason to have
get/set/has/clear methods for them. Clients and protos (while serializing) can
check against the invalid value to see if it's been set.

Change-Id: Ic63400889581271b8cbcd9c45c84519d4921fd4b

* commit '98c9208a616a97adf00bf1b3265e0f589c191d95':

* commit 'b6089cca5248f19832dde54faaad62891ff8bd25':

* commit '485b7645fea855d55b281185c7299ee9d7ab7f9a':

* commit 'c4c4a562672068fb89ea4e65408dd53de2ed8f1f':

* commit '0143d32d6ff0aad17873b486966c7a58efa04811':
  Align with main: two ways of parsing repeated packable fields.

* commit 'f5271c9ca4a237221c0ba722dc548050ad131064':
  Align with main: two ways of parsing repeated packable fields.

It is a requirement for parsing code to handle packed and unpacked
forms on the wire for repeated packable fields. This change aligns
the javanano's behavior with the java's.

Bonus: optimize array length calculation when parsing repeated
fixed-size-element-type fields.

Bonus 2: lose "xMemoizedSerializedSize" for repeated enum fields,
and make the serialized size calculation match that for repeated
int32 fields.

Change-Id: I8a06103d9290234adb46b0971b5ed155544fe86a

* commit '0afd5a4d782037ea641d75d595cf5d38ed6978ac':
  Update MessageNano#toString() to return mostly valid TextFormat.

* commit '3e0d99fab8c1da2a8f36637b7bf5e8581143e36a':
  Update MessageNano#toString() to return mostly valid TextFormat.

The output of toString is now aligned with that used by non-nano and C++
runtimes, with the exception of groups. Groups should be serialized using a
camelized name (e.g. "FooBar" rather than "foo_bar") however the nano runtime
does not have information on which fields are groups.

Changes are:
  - bytes fields are output within double-quotes, non-printable characters are
    output as octal escape sequences (i.e. \NNN);
  - field identifiers are output in underscored format;
  - unset fields are not output (rather than printing "null");
  - the type name of the root message is not output.

With these changes the nano toString, normal toString, and C++'s DebugString all
produce equivalent output when given the same message. (Provided that message
uses no deprecated features.)

Change-Id: Id4791d73822846db29344db9f7bc3781c3e183a6

* commit '382a066aa300b51cfd96c83ad53c49ce496d9d5c':
  Fix warnings warnings in header files, hide others.

* commit '332076f08a9d46b772fee755832a0e09dd8cb6aa':
  Fix warnings warnings in header files, hide others.

Follow upstream where they have any changes in 2.5.0

Change-Id: I3466e9c11242f533a9dff8c1afef4202dd100f2e

* commit '77e9fbd32c2732063a479acb50143a388a2321f0':
  Minimize method count for nanoproto.

* commit 'ac8e2e150716784a707587ae6e2c8b3a291a2ae7':
  Minimize method count for nanoproto.

- Migrates getCachedSize to the MessageNano parent class to save one method per message.
- Create ExtendableMessageNano parent class for protos with extensions, this saves the
getExtension and setExtension methods on the relevant messages.
- getSerializedSize's default case (with no fields to serialize) also migrate to the
parent class, which saves methods on empty messages.
- Container classes become interfaces to save the constructor.

Change-Id: I81f1a1b6d6a660096835e9df3ea20456655aab4a

* commit '42b5c369cd0559025938d07c73ca51d1c0c32f2e':
  Allow for ref-type arrays containing null elements.

* commit '8a15121c1077fe883f428bd27dee6b99e06e48b6':
  Allow for ref-type arrays containing null elements.