Lines Matching full:yaml
30 namespace yaml {
34 /// to/from a YAML mapping. For example:
53 /// to/from a YAML scalar where there is a one-to-one mapping between
54 /// in-memory values and a string in YAML. For example:
71 /// of bit values and the YAML representation is a flow sequence of
89 /// to/from a yaml scalar. For example:
121 /// to/from a YAML sequence. For example:
140 // The following is option and will cause generated YAML to use
147 /// to/from a list of YAML documents.
640 assert(Err.empty() && "invalid struct trying to be written as yaml");
790 // to [de]normalize an object for use with YAML conversion.
824 // to [de]normalize an object for use with YAML conversion.
860 /// The Input class is used to parse a yaml document into in-memory structs
863 /// It works by using YAMLParser to do a syntax parse of the entire yaml
865 /// each yaml Node. The extra layer is buffering. The low level yaml
873 // Construct a yaml Input object from a StringRef and optional
989 std::unique_ptr<llvm::yaml::Stream> Strm;
993 llvm::yaml::document_iterator DocIterator;
1003 /// The Output class is used to generate a yaml document from in-memory structs
1064 /// YAML I/O does conversion based on types. But often native data types
1067 /// look like a built in type. This will cause the generic YAML I/O conversion
1068 /// to be used. To provide better control over the YAML conversion, you can
1090 /// its yaml output formatted as hexadecimal.
1229 } // namespace yaml
1234 /// should be considered a YAML sequence.
1237 namespace yaml { \
1253 /// should be considered a YAML flow sequence.
1256 namespace yaml { \
1274 /// should be considered a YAML document list.
1277 namespace yaml { \
