1. 07 Mar, 2014 1 commit
  2. 10 Feb, 2014 1 commit
  3. 16 Jan, 2014 2 commits
  4. 14 Jan, 2014 3 commits
  5. 13 Jan, 2014 4 commits
  6. 10 Jan, 2014 2 commits
    • Max Cai's avatar
      Correctness: floating point equality using bits instead of ==. · 79b311c1
      Max Cai authored
      Special values for float and double make it inaccurate to test the equality with ==.
      The main Java library uses the standard Object.equals() implementation for all fields,
      which for floating point fields means Float.equals() or Double.equals(). They define
      equality as bitwise equality, with all NaN representations normalized to the same bit
      sequence (and therefore equal to each other). This test checks that the nano
      implementation complies with Object.equals(), so NaN == NaN and +0.0 != -0.0.
      
      Change-Id: I97bb4a3687223d8a212c70cd736436b9dd80c1d7
      79b311c1
    • Max Cai's avatar
      Don't serialize required fields whose 'has' flags are unset. · 1b1735ce
      Max Cai authored
      Change-Id: Ibbe944fff83e44a8f2206e18ee9ec6f10661297a
      1b1735ce
  7. 19 Dec, 2013 2 commits
  8. 12 Dec, 2013 1 commit
    • Andrew Flynn's avatar
      Fix MessageNanoPrinter for accessors · 02a9ea00
      Andrew Flynn authored
      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
      02a9ea00
  9. 10 Dec, 2013 5 commits
  10. 09 Dec, 2013 1 commit
    • Andrew Flynn's avatar
      Nano: don't generate accessor methods for nested methods · c997c136
      Andrew Flynn authored
      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
      c997c136
  11. 06 Dec, 2013 1 commit
  12. 05 Dec, 2013 1 commit
  13. 23 Nov, 2013 1 commit
  14. 22 Nov, 2013 1 commit
  15. 21 Nov, 2013 1 commit
  16. 18 Nov, 2013 2 commits
  17. 15 Nov, 2013 5 commits
  18. 13 Nov, 2013 1 commit
  19. 12 Nov, 2013 2 commits
  20. 11 Nov, 2013 1 commit
    • Tom Chao's avatar
      Minimize method count for nanoproto. · 28b4dec7
      Tom Chao authored
      - 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
      28b4dec7
  21. 07 Nov, 2013 1 commit
  22. 06 Nov, 2013 1 commit