- 07 Mar, 2016 1 commit
-
-
avgweb authored
-
- 15 Jan, 2016 1 commit
-
-
Jon Skeet authored
Previously we were incorrectly packing wrapper types. This also refactors FieldCodec a bit as well, using more C# 6-ness.
-
- 01 Oct, 2015 1 commit
-
-
Jon Skeet authored
This changes how we approach JSON formatting in general - instead of looking at the field a value came from, we just look at the type of the value. It's possible this *could* be slightly inefficient, but if we start caring about JSON performance deeply, we'll probably want to rewrite all of this anyway. It's definitely simpler this way. When we support dynamic messages, we'll need to modify JsonFormatter to handle enum values, as they won't come be "real" .NET enums at that point. It shouldn't be hard to do though.
-
- 08 Aug, 2015 1 commit
-
-
Jon Skeet authored
-
- 04 Aug, 2015 1 commit
-
-
Jon Skeet authored
-
- 30 Jul, 2015 3 commits
-
-
Jon Skeet authored
-
Jon Skeet authored
-
Jan Tattermusch authored
-
- 27 Jul, 2015 1 commit
-
-
Jon Skeet authored
This requires .NET 4.5, and there are a few compatibility changes required around reflection. Creating a PR from this to see how our CI systems handle it. Will want to add more documentation, validation and probably tests before merging. This is in aid of issue #590.
-
- 17 Jul, 2015 1 commit
-
-
Jon Skeet authored
We'll see what I've missed when CI fails...
-
- 16 Jul, 2015 3 commits
-
-
Jon Skeet authored
- We do still generate the message types, as otherwise reflection breaks, even though it doesn't actually use those types. - JSON handling hasn't been implemented yet
-
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.
-
Jan Tattermusch authored
-
- 09 Jul, 2015 2 commits
-
-
Jon Skeet authored
... and some implementation changes to go with them.
-
Jon Skeet authored
- FieldAccessorTable is now non-generic - We don't have a static field per message type in the umbrella class. (Message descriptors are accessed via the file descriptor.) - Removed the "descriptor assigner" complication from the descriptor fixup; without extensions, we don't need it - MapField implements IDictionary (more tests would be good...) - RepeatedField implements IList (more tests would be good) - Use expression trees to build accessors. (Will need to test this on various platforms... probably need a fallback strategy just using reflection directly.) - Added FieldDescriptor.IsMap - Added tests for reflection with generated messages Changes to generated code coming in next commit.
-
- 30 Jun, 2015 3 commits
-
-
Jon Skeet authored
Everything should now be consistent - the only difference between files is the year (aside from generated files). Fixes issue #531.
-
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.
-
Jon Skeet authored
Prod code works, but some tests are broken. Obviously those need fixing, then more tests, and review benchmarks.
-
- 26 Jun, 2015 2 commits
-
-
Jon Skeet authored
-
Jon Skeet authored
- Change the default message hash code to 1 to be consistent with other code - Change the empty list/map hash code to 0 as "empty map" is equivalent to "no map" - Removed map fields from unittest_proto3.proto - Created map_unittest_proto3.proto which is like map_unittest.proto but proto3-only - Fixed factory methods in FieldCodec highlighted by using all field types :) - Added tests for map serialization: - Extra fields within entries - Entries with value then key - Non-contiguous entries for the same map - Multiple entries for the same key Changes to generated code coming in next commit
-
- 24 Jun, 2015 1 commit
-
-
Jon Skeet authored
Fixes issue #523.
-
- 23 Jun, 2015 1 commit
-
-
Jon Skeet authored
Fixes issue #527.
-
- 19 Jun, 2015 1 commit
-
-
Jon Skeet authored
-
- 12 Jun, 2015 1 commit
-
-
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...)
-
- 09 Jun, 2015 1 commit
-
-
Jon Skeet authored
-