When running >bazel test :protobuf_test a few compiler warnings came up.  They were centered around the usage of "int" as the loop counter where the value should have been a size_t.

Docs: Link to Apple's Swift plugin and runtime for protobufs

Add note about extension use and Coding support.

Adds pushLimit: and popLimit: into GPBCodedInputStream

define no_threadlocal on OpenBSD

Support extra parameters for plugins.

Hacking ByteBufferWriter to work with GAE

Fixes #2269

Place Python extensions correctly in Bazel build.

Use git clean before installing via bundler

Need to expose generated protobuf C++ headers

Merge 3.1.x branch into master.

Declare all inputs of protoc action

ctx.executable.plugin must be in the inputs of protoc's action when using a plugin, otherwise the action will fail.

This bug has been hidden by a bug in Bazel: for every ctx.action, Bazel used to automatically add the runfiles of all executable inputs of the RULE instead of using the inputs of the specific ACTION. Consequently, we could get away with underspecifying the inputs of the action.

Fix MSVC build when HAVE_LONG_LONG is defined.

Merge 3.1.x branch into master.

Fix python_cpp test on Mac. Link staticly when building extension, so that the extension doesn't require installing protobuf library. (#2232)

* PHP: fix ZTS tsrm_ls errors

* Fix a few more macros

There seem to already be .proto files out there that have conflicting
enum names, which will not be able to build successfully for some
languages (like C#). To prevent this problem from spreading, let's make
it an error for proto3 but just issue a warning for proto2. This fixes
issue #2179.