Lines Matching full:be
37 A namespace declares which namespaces/package/module/etc. the type definitions in this file will be…
59 …eceding value for any subsequent element. Any constant value that is supplied must be non-negative.
65 Structs are the fundamental compositional type in Thrift. The name of each field must be unique wit…
81 …n handling mechanisms in the target languages. The name of each field must be unique within the ex…
109 - Write: Required fields are always written and are expected to be set.
110 - Read: Required fields are always read and are expected to be contained in the input stream.
115 … soft versioning. Because they must be present on read, the fields cannot be deprecated. If a requ…
120 - Read: Optional fields may, or may not be part of the input stream.
128 - Read: Like optional, the field may, or may not be part of the input stream.
129 - Default values: may not be written (see next section)
131 …be written ("req-out"), in reality unset fields are not always written. This is especially the cas…
135 …at initialization time. Therefore, a value that equals the default may not be written, because the…
252 Why can't `DefinitionType` be the same as `FieldType` (i.e. include `Identifier`)?
256 What to do about `ListSeparator`? Do we really want to be as lax as we currently are?
258 Should `Field*` really be `Field+` in `Struct`, `Enum`, etc.?