feat: fix parenthesis formatting issue (#132)

Author: Tbusk

docs/contributor-guide/compiler-guide/03-00-the-vala-compiler/03-02-parser.md

@@ -14,8 +14,8 @@ the parser is a hand-crafted recursive descent parser. The parser is in
 `vala/valaparser.vala` and its lexer is in `vala/valascanner.vala`.
 :::
 
-The entry point of the parser is `Vala.Parser.parse()`. This method is
-called by `Vala.Compiler.run()`. Vala.Parser is an implementation of
+The entry point of the parser is `Vala.Parser.parse ()`. This method is
+called by `Vala.Compiler.run ()`. Vala.Parser is an implementation of
 `Vala.CodeVisitor` for source files.
 
 ## 3.2.1. Visitors and Ping Pong
@@ -220,21 +220,21 @@ specializations of CodeNode may have children. The type and number of
 children are declared in the specialized class.
 
 The two important methods in a CodeNode are *accept* and
-*accept_children*. The accept() method lets the node declare to the
+*accept_children*. The accept () method lets the node declare to the
 CodeVisitor what it is, so the CodeVisitor can act on it. For example,
-Vala.Struct.accept():
+Vala.Struct.accept ():
 
 ```vala
 public override void accept (CodeVisitor visitor) {
      visitor.visit_struct (this); /* I am a struct! */
 }
 ```
 
-The accept_children() method lets the node accept all of its children so
+The accept_children () method lets the node accept all of its children so
 they can declare themselves to the CodeVisitor. This is the recursive
 part of the traversal. For example, a Struct code node has a list of
 base types, type parameters, fields, constants, and methods.
-Vala.Struct.accept_children() accepts all of these.
+Vala.Struct.accept_children () accepts all of these.
 
 ```vala
 public override void accept_children (CodeVisitor visitor) {
@@ -267,7 +267,7 @@ public override void accept_children (CodeVisitor visitor) {
 As you can see, the CodeVisitor is repeatedly asked to visit different
 code nodes. It can do whatever analysis is necessary and then traverse
 deeper into the code tree. This is what a hypothetical implementation of
-XmlGenerator.visit_struct() might look like:
+XmlGenerator.visit_struct () might look like:
 
 ```vala
 public override void visit_struct (Struct st) {
@@ -284,7 +284,7 @@ public override void visit_struct (Struct st) {
 ```
 
 The visit_ methods of a CodeVisitor needn't call
-CodeNode.accept_children(), if it isn't necessary to traverse the whole
+CodeNode.accept_children (), if it isn't necessary to traverse the whole
 depth of the code tree. It also isn't necessary to write visit_
 methods for every kind of code node, because empty implementations are
 already provided in CodeVisitor.

docs/contributor-guide/compiler-guide/03-00-the-vala-compiler/03-03-semantic-analyzer.md

@@ -13,10 +13,10 @@ are used in emitted C code.
 
 All attributes except for Conditional are handled from
 Vala.AttributeProcessor. I don't know where and how conditional is
-handled, but there is a function ignore_node() in Vala.CodeContext.
+handled, but there is a function ignore_node () in Vala.CodeContext.
 
 Vala.AttributeProcessor is a CodeVisitor which simply calls the
-process_attributes() method on every namespace, class, struct,
+process_attributes () method on every namespace, class, struct,
 interface, enum, method, constructor, parameter, property, delegate,
 constant, field, and signal that it visits.
 
@@ -26,7 +26,7 @@ the attribute is called "CCode", then the process_ccode_attributes()
 function will be called to parse the key-value pairs supplied.
 
 ::: info TODO
-Mention Vala.Parser.set_attributes()
+Mention Vala.Parser.set_attributes ()
 
 Feel free to help: [Vala Docs Repository](https://github.com/vala-lang/vala-docs).
 :::

docs/contributor-guide/compiler-guide/03-00-the-vala-compiler/03-04-symbol-resolution.md

@@ -31,19 +31,19 @@ when a class is visited, current_scope is set to that class's scope.
 
 When the parser parses a type, e.g. in the statement Gtk.Window
 main_window;, the type Gtk.Window is initially a Vala.UnresolvedType. In
-visit_data_type(), the UnresolvedType code node asks its parent to
-replace it with a new Vala.DataType created with resolve_type().
+visit_data_type (), the UnresolvedType code node asks its parent to
+replace it with a new Vala.DataType created with resolve_type ().
 
-UnresolvedTypes have UnresolvedSymbols. resolve_type() uses
-resolve_symbol() to find the Typesymbol referred to, and then wraps it
+UnresolvedTypes have UnresolvedSymbols.resolve_type () uses
+resolve_symbol () to find the Typesymbol referred to, and then wraps it
 in a new DataType object.
 
-resolve_symbol() is a recursive method which looks up an unresolved
+resolve_symbol () is a recursive method which looks up an unresolved
 symbol's name in the current scope and returns the corresponding
 Typesymbol. The base case is when the UnresolvedSymbol has no
 qualifiers, e.g. Window. The recursive case is when the symbol looks
 like Gtk.Window or Gtk.Orientation.HORIZONTAL. In
-Vala.Parser.parse_symbol_name(), the symbol is built inside-out, so
+Vala.Parser.parse_symbol_name (), the symbol is built inside-out, so
 Gtk.Orientation.HORIZONTAL is parsed as:
 
 ```vala
@@ -62,10 +62,10 @@ the symbol is not found there, then the scope of all imported namespaces
 is searched. If more than one imported namespace contains the symbol, an
 "ambiguous reference" error will be reported.
 
-In the recursive case, resolve_symbol() is called on the child node to
+In the recursive case, resolve_symbol () is called on the child node to
 give a parent scope, in which the symbol is looked up.
 
-One last function of SymbolResolver is in visit_variable_declarator() -
+One last function of SymbolResolver is in visit_variable_declarator () -
 to mark a variable type reference as "nullable" if the variable's
 type is a class, interface, array or error (reference type). This is
 used later by Vala.NullChecker.

docs/developer-guides/bindings/generating-a-vapi-with-gobject-introspection.md

@@ -107,8 +107,8 @@ If the icon name isn't known, a “broken image” icon will be
 displayed instead. If the current icon theme is changed, the icon
 will be updated appropriately.
 
-This function is a convenience wrapper around gtk_button_new() and
-gtk_button_set_image().</doc>
+This function is a convenience wrapper around gtk_button_new () and
+gtk_button_set_image ().</doc>
 <return-value transfer-ownership="none">
   <doc xml:space="preserve">a new #GtkButton displaying the themed icon</doc>
   <type name="Widget" c:type="GtkWidget*"/>

docs/developer-guides/bindings/writing-a-vapi-manually/02-00-getting-started/02-04-create-a-root-namespace.md

@@ -16,7 +16,7 @@ namespace, e.g.:
 
 ```vala
 void main () {
-    Foo.library_function();
+    Foo.library_function ();
 }
 ```
 

docs/developer-guides/bindings/writing-a-vapi-manually/04-00-recognizing-vala-semantics-in-c-code/04-02-enums-and-flags.md

@@ -110,9 +110,9 @@ var foo_enum = (Foo) FooExtended.C;
 In Vala, enums and flags may have member functions and constants.
 In particular, `strerr`-like functions are best converted to member functions.
 
-### Enum aliases and `to_string()`
+### Enum aliases and `to_string ()`
 
-The default function `to_string()` can cause problems if the enum has aliases (the C error `duplicate case` will trigger). So to solve this,
+The default function `to_string ()` can cause problems if the enum has aliases (the C error `duplicate case` will trigger). So to solve this,
 you can create additional constants after the enum has been declared to add the missing enum aliases.
 
 For example this enum:

docs/developer-guides/bindings/writing-a-vapi-manually/04-00-recognizing-vala-semantics-in-c-code/04-06-functions.md

@@ -6,10 +6,10 @@ VAPI file for the `sync` system call:
 
 ```vala
 [CCode (cname = "sync")]
-void sync();
+void sync ();
 ```
 
 The ccode attribute, `cname`, specifies the C name to use. This avoids
 `valac` appending the current namespace to the function name, ensuring
-that a call to `Posix.sync()` in vala will map to a call to `sync()` in
-C, and not to `posix_sync()`.
+that a call to `Posix.sync ()` in vala will map to a call to `sync ()` in
+C, and not to `posix_sync ()`.

docs/developer-guides/bindings/writing-a-vapi-manually/06-00-adding-vala-friendly-semantics/06-02-properties.md

@@ -6,8 +6,8 @@ implementations will provide a collection of functions to query state
 about the instance. These can be converted to properties given the
 following:
 
--   The `get` method has the signature `T get(I self)` and the set
-    method has the signature `void set(I self, T val)`. They need not
+-   The `get` method has the signature `T get (I self)` and the set
+    method has the signature `void set (I self, T val)`. They need not
     actually occur in pairs.
 -   The `get` method does not have side effects that are not obvious to
     the user.

docs/developer-guides/bindings/writing-a-vapi-manually/07-00-binding-a-c-function-s-parameter-and-return-types/07-02-structs.md

@@ -22,7 +22,7 @@ public struct Foo {
     public int x;
     public int y;
 };
-void compute_foo(Foo f);
+void compute_foo (Foo f);
 ```
 
 Very rarely a C library function is written to receive a struct passed
@@ -48,5 +48,5 @@ public struct Foo {
     public int x;
     public int y;
 }
-void compute_foo(Foo f);
+void compute_foo (Foo f);
 ```

docs/developer-guides/bindings/writing-a-vapi-manually/08-00-binding-a-c-struct-s-fields/08-04-function-pointers.md

@@ -18,7 +18,7 @@ typedef struct {
 
 ```vala
 [CCode (cname = "foo_func")]
-public delegate void FooFunc(int a);
+public delegate void FooFunc (int a);
 
 public struct Foo {
     [CCode (delegate_target_cname = "callback_context")]
@@ -44,7 +44,7 @@ typedef struct {
 
 ```vala
 [CCode (cname = "foo_func")]
-public delegate void FooFunc(int a);
+public delegate void FooFunc (int a);
 
 public struct Foo {
     [CCode (delegate_target_cname = "callback_context", delegate_target_destroy_notify_cname = "callback_free")]