1. 05 Aug, 2015 1 commit
  2. 03 Aug, 2015 1 commit
  3. 30 Jul, 2015 1 commit
  4. 17 Jul, 2015 1 commit
  5. 16 Jul, 2015 1 commit
    • Jon Skeet's avatar
      Remove the struct-based iterator for RepeatedField. · 78b452b7
      Jon Skeet authored
      We don't use it in the runtime or generated code anywhere now, so the extra small performance boost isn't as critical, and it has some undesirable consequences.
      
      The tests have needed to change as iterator block enumerators don't throw when we might expect them to.
      78b452b7
  6. 09 Jul, 2015 1 commit
  7. 30 Jun, 2015 1 commit
    • Jon Skeet's avatar
      Tidying up and extra tests. · f34d37a3
      Jon Skeet authored
      This is mostly just making things internal instead of public, removing and reordering a bunch of code in CodedInputStream/CodedOutputStream, and generally tidying up.
      f34d37a3
  8. 25 Jun, 2015 1 commit
  9. 24 Jun, 2015 1 commit
  10. 12 Jun, 2015 1 commit
    • Jon Skeet's avatar
      Reimplement RepeatedField<T> using an array as the backing store. · 7532f025
      Jon Skeet authored
      This is effectively reimplementing List<T>, but with a few advantages:
      - We know that an empty repeated field is common, so don't allocate an array until we need to
      - With direct access to the array, we can easily convert enum values to int without boxing
      - We can relax the restrictions over what happens if the repeated field is modified while iterating, avoiding so much checking
      
      This is somewhat risky, in that reimplementing a building block like this is *always* risky, but hey...
      (The performance benefits are significant...)
      7532f025
  11. 09 Jun, 2015 1 commit