deploy: 5edb1ef

Author: mkruskal-google

index.xml

@@ -73,8 +73,7 @@ Compiler invocation The protocol buffer compiler produces Objective-C output whe
 Compiler Invocation The protocol buffer compiler produces PHP output when invoked with the --php_out= command-line flag. The parameter to the --php_out= option is the directory where you want the compiler to write your PHP output. In order to conform to PSR-4, the compiler creates a sub-directory corresponding to the package defined in the proto file.</description></item><item><title>PHP API</title><link>https://protobuf.dev/reference/php/api-docs-link/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/php/api-docs-link/</guid><description/></item><item><title>Python Generated Code Guide</title><link>https://protobuf.dev/reference/python/python-generated/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/python/python-generated/</guid><description>Any differences between proto2, proto3, and Editions generated code are highlighted - note that these differences are in the generated code as described in this document, not the base message classes/interfaces, which are the same across all versions. You should read the proto2 language guide, proto3 language guide, and/or Editions guide before reading this document.
 The Python Protocol Buffers implementation is a little different from C++ and Java. In Python, the compiler only outputs code to build descriptors for the generated classes, and a Python metaclass does the real work.</description></item><item><title>Python Comparison</title><link>https://protobuf.dev/reference/python/python-comparison/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/python/python-comparison/</guid><description>Because of how proto data is serialized, you cannot rely on the wire representation of a proto message instance to determine if its content is the same as another instance. A subset of the ways that a wire-format proto message instance can vary include the following:
 The protobuf schema changes in certain ways. A map field stores its values in a different order. The binary is built with different flags (such as opt vs.</description></item><item><title>Python API</title><link>https://protobuf.dev/reference/python/api-docs-link/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/python/api-docs-link/</guid><description/></item><item><title>Ruby Generated Code Guide</title><link>https://protobuf.dev/reference/ruby/ruby-generated/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/ruby/ruby-generated/</guid><description>You should read the language guides for proto2, proto3, or editions before reading this document.
-The protocol compiler for Ruby emits Ruby source files that use a DSL to define the message schema. However the DSL is still subject to change. In this guide we only describe the API of the generated messages, and not the DSL.
-Compiler Invocation The protocol buffer compiler produces Ruby output when invoked with the --ruby_out= command-line flag.</description></item><item><title>Rust Generated Code Guide</title><link>https://protobuf.dev/reference/rust/rust-generated/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/rust/rust-generated/</guid><description>This page describes exactly what Rust code the protocol buffer compiler generates for any given protocol definition.
+Compiler Invocation The protocol buffer compiler produces Ruby output when invoked with the --ruby_out= command-line flag. The parameter to the --ruby_out= option is the directory where you want the compiler to write your Ruby output. The compiler creates a .rb file for each .proto file input. The names of the output files are computed by taking the name of the .</description></item><item><title>Rust Generated Code Guide</title><link>https://protobuf.dev/reference/rust/rust-generated/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/rust/rust-generated/</guid><description>This page describes exactly what Rust code the protocol buffer compiler generates for any given protocol definition.
 This document covers how the protocol buffer compiler generates Rust code for proto2, proto3, and protobuf editions. Any differences between proto2, proto3, and editions generated code are highlighted. You should read the proto2 language guide, proto3 language guide, or editions guide before reading this document.
 Protobuf Rust Protobuf Rust is an implementation of protocol buffers designed to be able to sit on top of other existing protocol buffer implementations that we refer to as &amp;lsquo;kernels&amp;rsquo;.</description></item><item><title>Redaction in Rust</title><link>https://protobuf.dev/reference/rust/rust-redaction/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/rust/rust-redaction/</guid><description>Use the standard fmt::Debug (&amp;quot;{:?}&amp;quot; in format strings) on Protobuf messages for human-readable strings for logging, error messages, exceptions, and similar use cases. The output of this debug info is not intended to be machine-readable (unlike TextFormat and JSON which are not be used for debug output).
 Using fmt::Debug enables redaction of some sensitive fields.

reference/ruby/index.xml

@@ -1,3 +1,2 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ruby Reference on Protocol Buffers Documentation</title><link>https://protobuf.dev/reference/ruby/</link><description>Recent content in Ruby Reference on Protocol Buffers Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://protobuf.dev/reference/ruby/index.xml" rel="self" type="application/rss+xml"/><item><title>Ruby Generated Code Guide</title><link>https://protobuf.dev/reference/ruby/ruby-generated/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/ruby/ruby-generated/</guid><description>You should read the language guides for proto2, proto3, or editions before reading this document.
-The protocol compiler for Ruby emits Ruby source files that use a DSL to define the message schema. However the DSL is still subject to change. In this guide we only describe the API of the generated messages, and not the DSL.
-Compiler Invocation The protocol buffer compiler produces Ruby output when invoked with the --ruby_out= command-line flag.</description></item></channel></rss>
+Compiler Invocation The protocol buffer compiler produces Ruby output when invoked with the --ruby_out= command-line flag. The parameter to the --ruby_out= option is the directory where you want the compiler to write your Ruby output. The compiler creates a .rb file for each .proto file input. The names of the output files are computed by taking the name of the .</description></item></channel></rss>