Lines Matching refs:proto3

137     converted to "lowerCamelCase" in proto3 JSON format. This option can be
140   * Added conformance tests to ensure implementations are following proto3 JSON
163       - Updated the JSON utility to comply with proto3 JSON specification.
166   * Added proto3 JSON format utility. It includes support for all field types
193   * Added proto3 support for JavaScript. The runtime is written in pure
207     the proto3 language guide:
209       https://developers.google.com/protocol-buffers/docs/proto3#json
212     proto3-conformant JSON serializers and parsers. Until then, do not rely
295     Most proto3 features supported:
306   * Introduced two new language implementations (Objective-C, C#) to proto3.
307   * Explicit "optional" keyword are disallowed in proto3 syntax, as fields are
309   * Group fields are no longer supported in proto3 syntax.
311     proto3 (implemented for C++, Java, Python in this release).  The user can
318   * Added a "reserved" keyword in both proto2 and proto3 syntax. User can use
346     field support(single, repeated, map, oneof), proto2 and proto3 syntax
359     * Only proto2 is supported in C# at the moment, proto3 support is in
407     Python) to proto3.
411     Python has received several updates, most notably support for proto3
412     semantics in any .proto file that declares syntax="proto3".
413     Messages declared in proto3 files no longer represent field presence
427     We have added proto3 support for Ruby via a native C extension.
466       The behavior is consistent with proto3 semantics.
489   * Introduced Protocol Buffers language version 3 (aka proto3).
493     started from v2.0.0. From v3.0.0, a new language version (proto3) is
496     The main intent of introducing proto3 is to clean up protobuf before
498     In proto3, the language is simplified, both for ease of use and  to
506          of required fields, and removal of default values. This makes proto3
519     This release (v3.0.0-alpha-1) includes partial proto3 support for C++ and
524     uses proto2 or proto3:
527       syntax = "proto3";
534     We recommend that new Protocol Buffers users use proto3. However, we do not
535     generally recommend that existing users migrate from proto2 from proto3 due
540     proto3).
552   * Added arena allocation support (for both proto2 and proto3).