283d9f7483
pin dependency github.com/beorn7/perks from v1.0.0 to v1.0.1 pin dependency github.com/golang/protobuf from v1.3.3 to v1.4.2 pin denpendency github.com/json-iterator/go from v1.1.8 to v1.1.9 pin dependency github.com/prometheus/common from v0.4.1 to v0.9.1 pin dependency github.com/prometheus/procfs from v0.0.5 to v0.0.11 pin dependency github.com/alecthomas/template from v0.0.0-20160405071501-a0175ee3bccc to v0.0.0-20190718012654-fb15b899a751 pin dependency github.com/alecthomas/units from v0.0.0-20151022065526-2efee857e7cf to v0.0.0-20190717042225-c3de453c63f4 pin dependency github.com/go-kit/kit from v0.8.0 to v0.9.0 pin dependency github.com/go-logfmt/logfmt from v0.3.0 to v0.4.0 Co-Authored-By: Jordan Liggitt <jordan@liggitt.net>
30 lines
1.4 KiB
Go
30 lines
1.4 KiB
Go
// Copyright 2018 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
// Package text implements the text format for protocol buffers.
|
|
// This package has no semantic understanding for protocol buffers and is only
|
|
// a parser and composer for the format.
|
|
//
|
|
// There is no formal specification for the protobuf text format, as such the
|
|
// C++ implementation (see google::protobuf::TextFormat) is the reference
|
|
// implementation of the text format.
|
|
//
|
|
// This package is neither a superset nor a subset of the C++ implementation.
|
|
// This implementation permits a more liberal grammar in some cases to be
|
|
// backwards compatible with the historical Go implementation.
|
|
// Future parsings unique to Go should not be added.
|
|
// Some grammars allowed by the C++ implementation are deliberately
|
|
// not implemented here because they are considered a bug by the protobuf team
|
|
// and should not be replicated.
|
|
//
|
|
// The Go implementation should implement a sufficient amount of the C++
|
|
// grammar such that the default text serialization by C++ can be parsed by Go.
|
|
// However, just because the C++ parser accepts some input does not mean that
|
|
// the Go implementation should as well.
|
|
//
|
|
// The text format is almost a superset of JSON except:
|
|
// * message keys are not quoted strings, but identifiers
|
|
// * the top-level value must be a message without the delimiters
|
|
package text
|