Auto-formatted all .mojom files.

mojo/public/interfaces/bindings/mojom_types.mojom

Index: mojo/public/interfaces/bindings/mojom_types.mojom
diff --git a/mojo/public/interfaces/bindings/mojom_types.mojom b/mojo/public/interfaces/bindings/mojom_types.mojom
index bd29dbcabb81d763ea5633c0bff18b10e1f6b3e6..b971fabebbb20a91677e6ba46ad220a4bd00724b 100644
--- a/mojo/public/interfaces/bindings/mojom_types.mojom
+++ b/mojo/public/interfaces/bindings/mojom_types.mojom
@@ -2,51 +2,51 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-[DartPackage="mojo", JavaPackage="org.chromium.mojo.bindings.types"]
+[DartPackage="mojo",
+JavaPackage="org.chromium.mojo.bindings.types"]
 module mojo.bindings.types;
 
-
 /*
-* This file contains definitions of data structures used to represent
-* Mojom types and values.
-*
-* As described in the Mojom Language Specification, Mojom types are defined
-* recursively and consequently a |Type| object may recursively contain
-* other |Type| objects. For example a |Type| object representing an array<int32>
-* will contain a |Type| object representing an int32.
-*
-* A Mojom type declaration may contain an identifier that resolves  to a
-* user-defined type: a struct, union, enum or interface. We use |TypeReference|
-* to represent an occurrence of such an identifier. A |TypeReference| may be
-* resolved or not. Resolved means that the user-defined type to which the
-* identifier refers has been found and associated with the |TypeReference|.
-* A |Type| object is fully-resolved if it, and recursively all of its
-* sub-components, do not contain any unresolved TypeReferences.
-*
-* A resolved |TypeReference| does not literally contain a structure representing
-* the user-defined type that it represents but rather refers to its target type
-* indirectly via a string called a |type_key|. The type_key may be used to
-* lookup the user-defined type to which it refers.
-*
-* The mapping from |type_keys| to user-defined types is not
-* represented by any structures in this file and instead must be maintained
-* by a higher layer context in which this file is used. For example the
-* |ServiceDescription| interface defined in service_describer.mojom includes
-* the method:
-*     GetTypeDefinition(string type_key) => UserDefinedType? type);
-* for this purpose.
-* We refer to this higher-layer context as the *owning context.*
-*
-* In addition to types, Mojom values are also representd by structures in this
-* file. A |Value| may be a LiteralValue, a UserValueReference or a
-* BuiltinConstantValue. Similarly to the situation with TypeReferences,
-* UserValueReferences contain a |value_key| which may be used to lookup
-* a UserDefinedValue (an EnumValue or a UserDefinedConstant) in
-* the owning context. For example the |MojomFileGraph| struct in
-* mojom_files.mojom contains the map:
-*     map<string, UserDefinedValue> resolved_values;
-* for this purpose.
-*/
+ * This file contains definitions of data structures used to represent
+ * Mojom types and values.
+ *
+ * As described in the Mojom Language Specification, Mojom types are defined
+ * recursively and consequently a |Type| object may recursively contain
+ * other |Type| objects. For example a |Type| object representing an array<int32>
+ * will contain a |Type| object representing an int32.
+ *
+ * A Mojom type declaration may contain an identifier that resolves  to a
+ * user-defined type: a struct, union, enum or interface. We use |TypeReference|
+ * to represent an occurrence of such an identifier. A |TypeReference| may be
+ * resolved or not. Resolved means that the user-defined type to which the
+ * identifier refers has been found and associated with the |TypeReference|.
+ * A |Type| object is fully-resolved if it, and recursively all of its
+ * sub-components, do not contain any unresolved TypeReferences.
+ *
+ * A resolved |TypeReference| does not literally contain a structure representing
+ * the user-defined type that it represents but rather refers to its target type
+ * indirectly via a string called a |type_key|. The type_key may be used to
+ * lookup the user-defined type to which it refers.
+ *
+ * The mapping from |type_keys| to user-defined types is not
+ * represented by any structures in this file and instead must be maintained
+ * by a higher layer context in which this file is used. For example the
+ * |ServiceDescription| interface defined in service_describer.mojom includes
+ * the method:
+ *     GetTypeDefinition(string type_key) => UserDefinedType? type);
+ * for this purpose.
+ * We refer to this higher-layer context as the *owning context.*
+ *
+ * In addition to types, Mojom values are also representd by structures in this
+ * file. A |Value| may be a LiteralValue, a UserValueReference or a
+ * BuiltinConstantValue. Similarly to the situation with TypeReferences,
+ * UserValueReferences contain a |value_key| which may be used to lookup
+ * a UserDefinedValue (an EnumValue or a UserDefinedConstant) in
+ * the owning context. For example the |MojomFileGraph| struct in
+ * mojom_files.mojom contains the map:
+ *     map<string, UserDefinedValue> resolved_values;
+ * for this purpose.
+ */
 
 // The different kinds of types. We divide the types into five categories:
 // simple, string, compound, handle, and user-defined.
@@ -78,7 +78,7 @@ enum SimpleType {
   UINT8,
   UINT16,
   UINT32,
-  UINT64
+  UINT64,
 };
 
 struct StringType {
@@ -136,7 +136,6 @@ struct TypeReference {
   // a Scope field to TypeReference so that resolution may occur later.
   string? identifier;
 
-
   // This field is non-null if this reference has been resolved.
   string? type_key;
 };
@@ -379,7 +378,6 @@ struct DeclaredConstant {
 // Declaration Data
 ////////////////////////////////////////////////////////////////////////////
 
-
 struct Attribute {
   string key;
 
@@ -400,7 +398,7 @@ struct DeclarationData {
   // for convenience as it can also be parsed from the |attributes| field.
   int32 min_version = -1; // Negative value means unset.
 
-  string? short_name;  // Some implementations may not provide names.
+  string? short_name; // Some implementations may not provide names.
 
   // The fully-qualified identifier is the concatenation of the names of the
   // containing scopes, starting from the module name, with a period ('.')