package google.protobuf.compiler

Get desktop application:
View/edit binary Protocol Buffers messages

• repeated MessageAccessInfo message = 1

An encoded CodeGeneratorRequest is written to the plugin's stdin.

• repeated string file_to_generate = 1

  The .proto files that were explicitly listed on the command-line. The code generator should generate code only for these files. Each file's descriptor will be included in proto_file, below.

• optional string parameter = 2

  The generator parameter passed on the command-line.

• repeated FileDescriptorProto proto_file = 15

  FileDescriptorProtos for all files in files_to_generate and everything they import. The files will appear in topological order, so each file appears before any file that imports it. protoc guarantees that all proto_files will be written after the fields above, even though this is not technically guaranteed by the protobuf wire format. This theoretically could allow a plugin to stream in the FileDescriptorProtos and handle them one by one rather than read the entire set into memory at once. However, as of this writing, this is not similarly optimized on protoc's end -- it will store all fields in memory at once before sending them to the plugin.

The plugin writes an encoded CodeGeneratorResponse to stdout.

• optional string error = 1

  Error message. If non-empty, code generation failed. The plugin process should exit with status code zero even if it reports an error in this way. This should be used to indicate errors in .proto files which prevent the code generator from generating correct code. Errors which indicate a problem in protoc itself -- such as the input CodeGeneratorRequest being unparseable -- should be reported by writing a message to stderr and exiting with a non-zero status code.

• repeated CodeGeneratorResponse.File file = 15

Represents a single generated file.

Used in: CodeGeneratorResponse

• optional string name = 1

  The file name, relative to the output directory. The name must not contain "." or ".." components and must be relative, not be absolute (so, the file cannot lie outside the output directory). "/" must be used as the path separator, not "\". If the name is omitted, the content will be appended to the previous file. This allows the generator to break large files into small chunks, and allows the generated text to be streamed back to protoc so that large files need not reside completely in memory at one time. Note that as of this writing protoc does not optimize for this -- it will read the entire CodeGeneratorResponse before writing files to disk.

• optional string insertion_point = 2

  If non-empty, indicates that the named file should already exist, and the content here is to be inserted into that file at a defined insertion point. This feature allows a code generator to extend the output produced by another code generator. The original generator may provide insertion points by placing special annotations in the file that look like: @@protoc_insertion_point(NAME) The annotation can have arbitrary text before and after it on the line, which allows it to be placed in a comment. NAME should be replaced with an identifier naming the point -- this is what other generators will use as the insertion_point. Code inserted at this point will be placed immediately above the line containing the insertion point (thus multiple insertions to the same point will come out in the order they were added). The double-@ is intended to make it unlikely that the generated code could contain things that look like insertion points by accident. For example, the C++ code generator places the following line in the .pb.h files that it generates: // @@protoc_insertion_point(namespace_scope) This line appears within the scope of the file's package namespace, but outside of any particular class. Another plugin can then specify the insertion_point "namespace_scope" to generate additional classes or other declarations that should be placed in this scope. Note that if the line containing the insertion point begins with whitespace, the same whitespace will be added to every line of the inserted text. This is useful for languages like Python, where indentation matters. In these languages, the insertion point comment should be indented the same amount as any inserted code will need to be in order to work correctly in that context. The code generator that generates the initial file and the one which inserts into it must both run as part of a single invocation of protoc. Code generators are executed in the order in which they appear on the command line. If |insertion_point| is present, |name| must also be present.

• optional string content = 15

  The file contents.

To convey the access pattern of a field, it classifies the type of the accessor methods into getters, setters and configs. Getters and setters read and write the field respectively and other operations like checking if the field exists are considered as configs.

Used in: MessageAccessInfo

• optional string name = 1

• optional uint64 getters_count = 2

• optional uint64 setters_count = 3

• optional uint64 configs_count = 4

"count" correlates with how many samples an access info has for a message. High "count" means more confident optimization based on the info.

Used in: AccessInfo

• optional string name = 1

• optional uint64 count = 2

• repeated FieldAccessInfo field = 3