We'll probably want a lot of the code from the serialization project when we do JSON, but enough of it will change that it's not worth keeping in a broken state for now.

Check HAVE_CONFIG_H before including "config.h"

Now the Build tool needs to define -DHAVE_ZLIB and -DHAVE-PTHREAD rather
than providing a config.h

- Make pbconfig.h a manually written file to handle hash conditions
  according to platform related macros.
- Remove #include "config.h" from source code.
- Changed the configure.ac and Makefile.am to pass down the macros.
- Change cmake to pass down the the macros.

Change-Id: I537249d5df8fdeba189706aec436d1ab1104a4dc

Add a badge for AppVeyor build.

Modified FindRubyTestDir to use GOOGLE_THIRD_PARTY_PROTOBUF

Change-Id: Ic59d78d699af0e5f50377f83c8a7ea9a78074d81

Remove config.h.include which is no longer needed

Change-Id: I2015df2409aa95401af658b40023c8f9b9d75068

generated file now.

Change-Id: I68b397e7fa9248abc93d5c12efd5cd31e380c9ab

Make pbconfig.h independent of config.h

Change-Id: I31ead985b4ac5b02fb7558d34c1da19fd837b50a

Workaround for MSVC's string literal compiler limit.

Give descriptor.proto a go package

Escape characters don't count for string literal size, no need to pre-generate escape string.

Added unit test to touch enormous cpp generated descriptor.

Updated makefile to include enormous_descriptor.proto

Fixed language compatibility error.

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...)

I wouldn't expect this to affect anything, but it appears to.

This is currently done in golang/protobuf using `sed`. This change
should simplify things.

This mirrors commit 7c86bbbc7a3365c034d82173b38ec4427b98b3b2 in the pull request to
the main protobuf project, but also reduces the size of the buffer created. (There's no point in
creating a 1024-byte buffer if we're only skipping 5 bytes...)

Remove ICodedInputStream and ICodedOutputStream, and rewrite CodedInputStream and CodedOutputStream to be specific to the binary format. If we want to support text-based formats, that can be a whole different serialization mechanism.

This makes repeated fields really awkward at the moment - but when we reimplement RepeatedField<T> to be backed by an array, we can cast the array directly...

Aside from anything else, this will be used for all tags for fields 1-15.

Cache a reference to Encoding.UTF8 - the property access is (rather surprisingly) significant.
Additionally, when we detect that the string is all ASCII (due to the computed length in bytes being the length in characters), we can perform the encoding very efficiently ourselves.

Update podspec, rename assets to drop @