Skip to content

Commit 5134ecc

Browse files
LogofileLogofile
committed
deploy: 13bf22c 
1 parent f98e374 commit 5134ecc

File tree

4 files changed

+201
-37
lines changed

4 files changed

+201
-37
lines changed

‎index.xml‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,8 +95,9 @@ Lexical Elements Letters and Digits letter = "A" ... "Z&
9595
Note This is a draft spec reverse-engineered from the C++ text format implementation and may change based on further discussion and review. While an effort has been made to keep text formats consistent across supported languages, incompatibilities are likely to exist. Example convolution_benchmark { label: &amp;#34;NHWC_128x20x20x56x160&amp;#34; input { dimension: [128, 56, 20, 20] data_type: DATA_HALF format: TENSOR_NHWC } } Parsing Overview The language elements in this spec are split into lexical and syntactic categories.</description></item><item><title>Protocol Buffers Well-Known Types</title><link>https://protobuf.dev/reference/protobuf/google.protobuf/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/google.protobuf/</guid><description>Index Any (message) Api (message) BoolValue (message) BytesValue (message) DoubleValue (message) Duration (message) Empty (message) Enum (message) EnumValue (message) Field (message) Field.Cardinality (enum) Field.Kind (enum) FieldMask (message) FloatValue (message) Int32Value (message) Int64Value (message) ListValue (message) Method (message) Mixin (message) NullValue (enum) Option (message) SourceContext (message) StringValue (message) Struct (message) Syntax (enum) Timestamp (message) Type (message) UInt32Value (message) UInt64Value (message) Value (message) Well-Known Types that end in &amp;ldquo;Value&amp;rdquo; are wrapper messages for other types, such as BoolValue and EnumValue.</description></item><item><title>Other Languages</title><link>https://protobuf.dev/reference/other/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/other/</guid><description>While the current release includes compilers and APIs for C++, Java, Go, Ruby, C#, and Python, the compiler code is designed so that it&amp;rsquo;s easy to add support for other languages. There are several ongoing projects to add new language implementations to Protocol Buffers, including C, Haskell, Perl, Rust, and more.
9696
For a list of links to projects we know about, see the third-party add-ons wiki page.
9797
Compiler Plugins protoc, the Protocol Buffers Compiler, can be extended to support new languages via plugins.</description></item><item><title>Version Support</title><link>https://protobuf.dev/support/version-support/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/version-support/</guid><description>Support windows for protoc and the various languages are covered in the tables later in this topic. Version numbers throughout this topic use SemVer conventions; in the version &amp;ldquo;3.21.7,&amp;rdquo; we say that &amp;ldquo;3&amp;rdquo; is the major version, &amp;ldquo;21&amp;rdquo; is the minor version, and &amp;ldquo;7&amp;rdquo; is the micro or patch number.
98-
Starting with the v20.x protoc release, we changed our versioning scheme to enable nimbler updates to language-specific parts of Protocol Buffers.</description></item><item><title>Migration Guide</title><link>https://protobuf.dev/support/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/migration/</guid><description>Compiler Changes in v22.0 JSON Field Name Conflicts Source of changes: PR #11349, PR #10750
99-
We&amp;rsquo;ve made some subtle changes in how we handle field name conflicts with respect to JSON mappings. In proto3, we&amp;rsquo;ve partially loosened the restrictions and only give errors when field names produce case-sensitive JSON mappings (camel case of the original name). We now also check the json_name option, and give errors for case-sensitive conflicts. In proto2, we&amp;rsquo;ve tightened restrictions a bit and will give errors if two json_name specifications conflict.</description></item><item><title>Cross-Version Runtime Guarantee</title><link>https://protobuf.dev/support/cross-version-runtime-guarantee/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/cross-version-runtime-guarantee/</guid><description>Protobuf language bindings have two components. The generated code (typically produced from protoc) and the runtime libraries that must be included when using the generated code. When these come from different releases of protobuf, we are in a &amp;ldquo;cross version runtime&amp;rdquo; situation.
98+
Starting with the v20.x protoc release, we changed our versioning scheme to enable nimbler updates to language-specific parts of Protocol Buffers.</description></item><item><title>Migration Guide</title><link>https://protobuf.dev/support/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/migration/</guid><description>Changes in v30.0 The following is a list of the breaking changes made to versions of the libraries, and how to update your code to accommodate the changes.
99+
This covers breaking changes announced in News Announcements for v30.x and Release Notes for v30.0.
100+
Replaced CMake Submodules with Fetched Deps Previously, our default CMake behavior was to use Git submodules to grab pinned dependencies. Specifying -Dprotobuf_ABSL_PROVIDER=package would flip our CMake configs to look for local installations of Abseil (with similar options for jsoncpp and gtest).</description></item><item><title>Cross-Version Runtime Guarantee</title><link>https://protobuf.dev/support/cross-version-runtime-guarantee/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/cross-version-runtime-guarantee/</guid><description>Protobuf language bindings have two components. The generated code (typically produced from protoc) and the runtime libraries that must be included when using the generated code. When these come from different releases of protobuf, we are in a &amp;ldquo;cross version runtime&amp;rdquo; situation.
100101
We intend to offer the following guarantees across all languages except C++. These are the default guarantees; however, owners of protobuf code generators and runtimes may explicitly override them with more specific guarantees for that language.</description></item><item><title>Downloads</title><link>https://protobuf.dev/downloads/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/downloads/</guid><description>Release Packages Latest Version The latest release of Protocol Buffers can be found on the release page.
101102
Old Versions Older versions are available in our historical releases on GitHub.
102103
Source Code GitHub Repository Protocol Buffers source code is hosted on GitHub.</description></item><item><title>History</title><link>https://protobuf.dev/history/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/history/</guid><description>Understanding why protobuf was created and the decisions that changed it over time can help you to better use the features of the tool.

‎reference/java/java-generated/index.html‎

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -269,14 +269,15 @@
269269
.proto file.</li><li><code>static ChoiceCase forNumber(int value)</code>: Returns the enum object
270270
corresponding to the given numeric value (or <code>null</code> for other numeric
271271
values).</li></ul><p>The compiler will generate the following accessor methods in both the message
272-
class and its builder:</p><ul><li><code>boolean hasFooInt()</code>: Returns <code>true</code> if the oneof case is <code>FOO</code>.</li><li><code>int getFooInt()</code>: Returns the current value of <code>foo</code> if the oneof case is
273-
<code>FOO</code>. Otherwise, returns the default value of this field.</li><li><code>ChoiceCase getChoiceCase()</code>: Returns the enum indicating which field is
272+
class and its builder:</p><ul><li><code>boolean hasFooInt()</code>: Returns <code>true</code> if the oneof case is <code>FOO_INT</code>.</li><li><code>int getFooInt()</code>: Returns the current value of <code>foo</code> if the oneof case is
273+
<code>FOO_INT</code>. Otherwise, returns the default value of this field.</li><li><code>ChoiceCase getChoiceCase()</code>: Returns the enum indicating which field is
274274
set. Returns <code>CHOICE_NOT_SET</code> if none of them is set.</li></ul><p>The compiler will generate the following methods only in the message&rsquo;s builder:</p><ul><li><code>Builder setFooInt(int value)</code>: Sets <code>Foo</code> to this value and sets the oneof
275-
case to <code>FOO</code>. After calling this, <code>hasFooInt()</code> will return <code>true</code>,
276-
<code>getFooInt()</code> will return <code>value</code> and <code>getChoiceCase()</code> will return <code>FOO</code>.</li><li><code>Builder clearFooInt()</code>:<ul><li>Nothing will be changed if the oneof case is not <code>FOO</code>.</li><li>If the oneof case is <code>FOO</code>, sets <code>Foo</code> to null and the oneof case to
277-
<code>FOO_NOT_SET</code>. After calling this, <code>hasFooInt()</code> will return <code>false</code>,
275+
case to <code>FOO_INT</code>. After calling this, <code>hasFooInt()</code> will return <code>true</code>,
276+
<code>getFooInt()</code> will return <code>value</code> and <code>getChoiceCase()</code> will return
277+
<code>FOO_INT</code>.</li><li><code>Builder clearFooInt()</code>:<ul><li>Nothing will be changed if the oneof case is not <code>FOO_INT</code>.</li><li>If the oneof case is <code>FOO_INT</code>, sets <code>Foo</code> to null and the oneof case to
278+
<code>CHOICE_NOT_SET</code>. After calling this, <code>hasFooInt()</code> will return <code>false</code>,
278279
<code>getFooInt()</code> will return the default value and <code>getChoiceCase()</code> will
279-
return <code>FOO_NOT_SET</code>.</li></ul></li><li><code>Builder.clearChoice()</code>: Resets the value for <code>choice</code>, returning the
280+
return <code>CHOICE_NOT_SET</code>.</li></ul></li><li><code>Builder.clearChoice()</code>: Resets the value for <code>choice</code>, returning the
280281
builder.</li></ul><p>For other simple field types, the corresponding Java type is chosen according to
281282
the
282283
<a href=/programming-guides/proto2#scalar>scalar value types table</a>.

‎support/index.xml‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Support on Protocol Buffers Documentation</title><link>https://protobuf.dev/support/</link><description>Recent content in Support on Protocol Buffers Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://protobuf.dev/support/index.xml" rel="self" type="application/rss+xml"/><item><title>Version Support</title><link>https://protobuf.dev/support/version-support/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/version-support/</guid><description>Support windows for protoc and the various languages are covered in the tables later in this topic. Version numbers throughout this topic use SemVer conventions; in the version &amp;ldquo;3.21.7,&amp;rdquo; we say that &amp;ldquo;3&amp;rdquo; is the major version, &amp;ldquo;21&amp;rdquo; is the minor version, and &amp;ldquo;7&amp;rdquo; is the micro or patch number.
2-
Starting with the v20.x protoc release, we changed our versioning scheme to enable nimbler updates to language-specific parts of Protocol Buffers.</description></item><item><title>Migration Guide</title><link>https://protobuf.dev/support/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/migration/</guid><description>Compiler Changes in v22.0 JSON Field Name Conflicts Source of changes: PR #11349, PR #10750
3-
We&amp;rsquo;ve made some subtle changes in how we handle field name conflicts with respect to JSON mappings. In proto3, we&amp;rsquo;ve partially loosened the restrictions and only give errors when field names produce case-sensitive JSON mappings (camel case of the original name). We now also check the json_name option, and give errors for case-sensitive conflicts. In proto2, we&amp;rsquo;ve tightened restrictions a bit and will give errors if two json_name specifications conflict.</description></item><item><title>Cross-Version Runtime Guarantee</title><link>https://protobuf.dev/support/cross-version-runtime-guarantee/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/cross-version-runtime-guarantee/</guid><description>Protobuf language bindings have two components. The generated code (typically produced from protoc) and the runtime libraries that must be included when using the generated code. When these come from different releases of protobuf, we are in a &amp;ldquo;cross version runtime&amp;rdquo; situation.
2+
Starting with the v20.x protoc release, we changed our versioning scheme to enable nimbler updates to language-specific parts of Protocol Buffers.</description></item><item><title>Migration Guide</title><link>https://protobuf.dev/support/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/migration/</guid><description>Changes in v30.0 The following is a list of the breaking changes made to versions of the libraries, and how to update your code to accommodate the changes.
3+
This covers breaking changes announced in News Announcements for v30.x and Release Notes for v30.0.
4+
Replaced CMake Submodules with Fetched Deps Previously, our default CMake behavior was to use Git submodules to grab pinned dependencies. Specifying -Dprotobuf_ABSL_PROVIDER=package would flip our CMake configs to look for local installations of Abseil (with similar options for jsoncpp and gtest).</description></item><item><title>Cross-Version Runtime Guarantee</title><link>https://protobuf.dev/support/cross-version-runtime-guarantee/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/cross-version-runtime-guarantee/</guid><description>Protobuf language bindings have two components. The generated code (typically produced from protoc) and the runtime libraries that must be included when using the generated code. When these come from different releases of protobuf, we are in a &amp;ldquo;cross version runtime&amp;rdquo; situation.
45
We intend to offer the following guarantees across all languages except C++. These are the default guarantees; however, owners of protobuf code generators and runtimes may explicitly override them with more specific guarantees for that language.</description></item></channel></rss>

‎support/migration/index.html‎

Lines changed: 188 additions & 27 deletions
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)