fix: apply white-space fixes from pre-commit run --all'

.clang-format

@@ -3,4 +3,4 @@ BasedOnStyle:  Google
 
 # Customize with larger indents
 IndentWidth:     4
-ObjCBlockIndentWidth: 4
+ObjCBlockIndentWidth: 4

.github/CODEOWNERS

@@ -4,4 +4,3 @@
 # Changes to `fetch-configlet` should be made in the `exercism/configlet` repo
 bin/fetch-configlet     @exercism/maintainers-admin
 bin/fetch-configlet.ps1 @exercism/maintainers-admin
-

.github/workflows/ci.yml

@@ -88,4 +88,3 @@ jobs:
         cmake .
         cmake --build . -- test_hello-world
         cmake --build .
-

.github/workflows/hello-world.yml

@@ -25,4 +25,4 @@ jobs:
     - name: Check Hello World Fails
       run: bin/check-hello-world.sh
       env:
-        CXX: ${{ matrix.compiler }}
+        CXX: ${{ matrix.compiler }}

.github/workflows/pre-commit.yml

@@ -30,4 +30,3 @@ jobs:
         uses: pre-commit/[email protected]
         with:
           extra_args: --all
-

.pre-commit-config.yaml

@@ -13,4 +13,3 @@ repos:
     hooks:
     -   id: clang-format
         exclude_types: [json]
-

.vscode/settings.json

@@ -72,4 +72,4 @@
     "cSpell.words": [
         "stationprogress"
     ]
-}
+}

bin/check-hello-world.sh

@@ -25,4 +25,4 @@ if cmake --build .; then
     exit 1
 fi
 
-cd "$repo"
+cd "$repo"

concepts/auto/links.json

@@ -7,4 +7,4 @@
         "url": "https://www.learncpp.com/cpp-tutorial/type-deduction-for-objects-using-the-auto-keyword/",
         "description": "Learn C++ overview on the auto keyword and its usage"
     }
-]
+]

concepts/basics/about.md

@@ -6,7 +6,7 @@ To set off the C++ journey we are starting with variables, function calls, and c
 
 Comments come in two flavors: single- and multi-line.
 Everything that comes after `//` on the same line is ignored by the compiler.
-Multi-line comments are also known as C-style comments. 
+Multi-line comments are also known as C-style comments.
 They are surrounded by `/*` and `*/`.
 Anything that comes between these will be ignored as well.
 
@@ -40,7 +40,7 @@ It cannot be stressed enough: avoid undefined behavior at all cost.
 
 ## Arithmetic Operations
 
-Arithmetic operators like `*`, `+`, or `-` can be part of an expression like `3 * 2` or `tomatoes + potatoes`. 
+Arithmetic operators like `*`, `+`, or `-` can be part of an expression like `3 * 2` or `tomatoes + potatoes`.
 
 ## Updating Variables
 
@@ -84,7 +84,7 @@ int total_fee(int vips, int adults, int kids) {
     */
     int standard_fee{30};
     int kids_discount{15};
-    
+
     int kids_total_fee = kids  * (standard_fee - kids_discount);
     int vips_total_fee = vips * vip_fee(standard_fee);
     int adult_total_fee = adults * standard_fee;

concepts/basics/introduction.md

@@ -6,7 +6,7 @@ To set off the C++ journey we are starting with variables, function calls, and c
 
 Comments come in two flavors: single- and multi-line.
 Everything that comes after `//` on the same line is ignored by the compiler.
-Multi-line comments are also known as C-style comments. 
+Multi-line comments are also known as C-style comments.
 They are surrounded by `/*` and `*/`.
 Anything that comes between these will be ignored as well.
 
@@ -40,7 +40,7 @@ It cannot be stressed enough: avoid undefined behavior at all cost.
 
 ## Arithmetic Operations
 
-Arithmetic operators like `*`, `+`, or `-` can be part of an expression like `3 * 2` or `tomatoes + potatoes`. 
+Arithmetic operators like `*`, `+`, or `-` can be part of an expression like `3 * 2` or `tomatoes + potatoes`.
 
 ## Updating Variables
 
@@ -84,7 +84,7 @@ int total_fee(int vips, int adults, int kids) {
     */
     int standard_fee{30};
     int kids_discount{15};
-    
+
     int kids_total_fee = kids  * (standard_fee - kids_discount);
     int vips_total_fee = vips * vip_fee(standard_fee);
     int adult_total_fee = adults * standard_fee;

concepts/basics/links.json

@@ -11,4 +11,4 @@
         "url": "https://isocpp.org/faq",
         "description": "C++ Super-FAQ"
     }
-]
+]

concepts/booleans/introduction.md

@@ -35,4 +35,4 @@ If you use a number in a Boolean operation, everything except `0` is treated as
 !true && 0.0   // => false
 true + true + false // => 2
 ```
-~~~~
+~~~~

concepts/booleans/links.json

@@ -3,4 +3,4 @@
         "url": "https://en.cppreference.com/w/cpp/language/operator_logical",
         "description": "C++ reference on Logical operators"
     }
-]
+]

concepts/classes/about.md

@@ -52,7 +52,7 @@ silverhand.cast_spell();
 silverhand.name = "Laeral";
 
 // damage is private:
-silverhand.damage = 500; 
+silverhand.damage = 500;
  // => Compilation error
 ```
 

concepts/classes/introduction.md

@@ -51,7 +51,7 @@ silverhand.cast_spell();
 silverhand.name = "Laeral";
 
 // damage is private:
-silverhand.damage = 500; 
+silverhand.damage = 500;
  // => Compilation error
 ```
 
@@ -102,4 +102,4 @@ Conventionally, the `struct` keyword is often used for **data-only structures**.
 The `class` keyword is preferred for objects that need to ensure certain properties.
 Such an invariant could be that the `damage` of your `Wizzard` `class` cannot turn negative.
 The `damage` variable is private and any function that changes the damage would ensure the invariant is preserved.
-~~~~
+~~~~

concepts/classes/links.json

@@ -3,4 +3,4 @@
         "url": "https://en.cppreference.com/w/cpp/language/classes",
         "description": "C++ reference on for classes"
     }
-]
+]

concepts/comparisons/about.md

@@ -27,7 +27,7 @@ Here are some common examples:
 ```cpp
 bool eq3 = 2 == 3; // false, integer comparison
 
-bool eq4 = 2.1 != 2.2; // true, float comparison 
+bool eq4 = 2.1 != 2.2; // true, float comparison
 
 bool eq5 = "hello" == "hello"; // true, string comparison
 ```

concepts/comparisons/introduction.md

@@ -27,7 +27,7 @@ Here are some common examples:
 ```cpp
 bool eq3 = 2 == 3; // false, integer comparison
 
-bool eq4 = 2.1 != 2.2; // true, float comparison 
+bool eq4 = 2.1 != 2.2; // true, float comparison
 
 bool eq5 = "hello" == "hello"; // true, string comparison
 ```

concepts/comparisons/links.json

@@ -3,4 +3,4 @@
         "url": "https://en.cppreference.com/w/cpp/language/operator_comparison",
         "description": "C++ reference on comparison operators"
     }
-]
+]

concepts/enums/about.md

@@ -46,7 +46,7 @@ enum class WheelMaterial {
     plastic
 };
 ```
-Although the wheels and the deck can both be made of _plastic_, the two cannot be confused. 
+Although the wheels and the deck can both be made of _plastic_, the two cannot be confused.
 They are different _types_:  `DeckMaterial` plastic and `WheelMaterial` plastic.
 Each `enumeration` will have its `enumerators` in its own scope - its own `namespace`.
 This is the reason they are called `scoped enumerations`.
@@ -57,7 +57,7 @@ You might be thinking that with a name like `scoped`, there would also be  _`uns
 `Unscoped enumerations` are becoming less popular because they all share the same global namespace.
 Because of the sharing, you could not have two `unscoped enumerations` with the same `enumerators` like _plastic_ in the example above.
 
-Also, `unscoped enumerations` implicitly convert to integers. 
+Also, `unscoped enumerations` implicitly convert to integers.
 Look at the example below for a surprising result:
 
 ```cpp
@@ -84,4 +84,4 @@ If you want to convert `scoped enumerations` to integers you can use `static_cas
 
 
 
-[magic numbers]: https://en.wikipedia.org/wiki/Magic_number_(programming)
+[magic numbers]: https://en.wikipedia.org/wiki/Magic_number_(programming)

concepts/enums/introduction.md

@@ -46,7 +46,7 @@ enum class WheelMaterial {
     plastic
 };
 ```
-Although the wheels and the deck can both be made of _plastic_, the two cannot be confused. 
+Although the wheels and the deck can both be made of _plastic_, the two cannot be confused.
 They are different _types_:  `DeckMaterial` plastic and `WheelMaterial` plastic.
 Each `enumeration` will have its `enumerators` in its own scope - its own `namespace`.
 This is the reason they are called `scoped enumerations`.
@@ -57,7 +57,7 @@ You might be thinking that with the name `scoped`, there would also be be `unsco
 `Unscoped enumerations` are becoming less popular because they all share the same global namespace.
 Because of the sharing, you could not have two `unscoped enumerations` with the same `enumerators` like _plastic_ in the example above.
 
-Also, `unscoped enumerations` implicitly convert to integers. 
+Also, `unscoped enumerations` implicitly convert to integers.
 Look at the example below for a surprising result:
 
 ```cpp
@@ -84,4 +84,4 @@ If you want to convert `scoped enumerations` to integers you can use `static_cas
 
 
 
-[magic numbers]: https://en.wikipedia.org/wiki/Magic_number_(programming)
+[magic numbers]: https://en.wikipedia.org/wiki/Magic_number_(programming)

concepts/enums/links.json

@@ -3,4 +3,4 @@
         "url": "https://en.cppreference.com/w/cpp/language/enum",
         "description": "C++ reference on enumerations"
     }
-]
+]

concepts/functions/links.json

@@ -15,4 +15,4 @@
         "url": "https://en.cppreference.com/w/cpp/language/default_arguments",
         "description": "C++ reference on default arguments"
     }
-]
+]

concepts/headers/about.md

@@ -10,7 +10,7 @@ The header file will tell you _what_ a codebase has to offer without going into
 The most common file extension for header files is `.h`.
 Some projects use `.hpp` or skip the extension completely.
 
-The definitions are located in a separate `.cpp` file. 
+The definitions are located in a separate `.cpp` file.
 To reunite the parts, the source file starts by _including_ the respective header file.
 
 If you want to write a library called "quick_math" that offers a function "super_root" that you want to use often, the files would look like this:
@@ -81,7 +81,7 @@ int robots::Flower::get_size() {return size;}
 When the header is used as an API overview, that is where a person would look for information like default values.
 The `size` parameter's default of the constructor is therefore handled in the header and not in the implementation.
 The definitions in the source file are prefixed with the namespace `robots` and the class type `Flower`.
- 
+
 Another layout option is a _header only_ library, that does not have a `.cpp` file at all:
 
 ```cpp
@@ -164,7 +164,7 @@ int myOtherFunction(int m) {
 
 It does not matter if the same file is included multiple times within a project.
 Header files should not contain definitions.
-The complete project cannot have the same definition more than once. 
+The complete project cannot have the same definition more than once.
 This is called the "One definition rule".
 It will be enforced by the compiler.
 
@@ -184,4 +184,4 @@ The syntax can be seen below with `MY_HEADER_FILE_H` as a variable.
 
 The problem with `#pragma once` is, that pragmas are not an official part of the C++ language and the implementation differs from compiler to compiler.
 Many big projects have switched to the simpler pragma method, but a few are still cautious.
-~~~~
+~~~~

concepts/headers/introduction.md

@@ -10,7 +10,7 @@ The header file will tell you _what_ a codebase has to offer without going into
 The most common file extension for header files is `.h`.
 Some projects use `.hpp` or skip the extension completely.
 
-The definitions are located in a separate `.cpp` file. 
+The definitions are located in a separate `.cpp` file.
 To reunite the parts, the source file starts by _including_ the respective header file.
 
 If you want to write a library called "quick_math" that offers a function "super_root" that you want to use often, the files would look like this:
@@ -81,7 +81,7 @@ int robots::Flower::get_size() {return size;}
 When the header is used as an API overview, that is where a person would look for information like default values.
 The `size` parameter's default of the constructor is therefore handled in the header and not in the implementation.
 The definitions in the source file are prefixed with the namespace `robots` and the class type `Flower`.
- 
+
 Another layout option is a _header only_ library, that does not have a `.cpp` file at all:
 
 ```cpp

concepts/headers/links.json

@@ -7,4 +7,4 @@
         "url": "https://www.learncpp.com/cpp-tutorial/classes-and-header-files/",
         "description": "More information about classes in header files"
     }
-]
+]

concepts/if-statements/about.md

@@ -41,4 +41,4 @@ if (int v{2 * num}; v > 10) {
 // => 14
 ```
 
-> Note: any variables created in the initialization cannot be accesed after the end of the if statement.
+> Note: any variables created in the initialization cannot be accesed after the end of the if statement.

concepts/if-statements/introduction.md

@@ -41,4 +41,4 @@ if (int v{2 * num}; v > 10) {
 // => 14
 ```
 
-> Note: any variables created in the initialization cannot be accesed after the end of the if statement.
+> Note: any variables created in the initialization cannot be accesed after the end of the if statement.

concepts/if-statements/links.json

@@ -3,4 +3,4 @@
         "url": "https://en.cppreference.com/w/cpp/language/if",
         "description": "C++ reference on if statements"
     }
-]
+]

concepts/includes/about.md

@@ -8,7 +8,7 @@ During compilation, the line with the directive is replaced by the content of th
 Namespaces are kept as they are in the original file after includes.
 
 ## The Standard Library
- 
+
 The standard library offers many common functions, algorithms, and data structures.
 The standard library uses the `std` namespace.
 

concepts/includes/introduction.md

@@ -11,7 +11,7 @@ During compilation, the line with the directive is replaced by the content of th
 Namespaces are kept as they are in the original file after includes.
 
 ## The Standard Library
- 
+
 The standard library offers many common functions, algorithms, and data structures.
 The standard library uses the `std` namespace.
 

concepts/includes/links.json

@@ -3,4 +3,4 @@
         "url": "https://en.cppreference.com/w/cpp/preprocessor/include",
         "description": "C++ reference on Source File Inclusion"
     }
-]
+]

concepts/loops/about.md

@@ -63,7 +63,7 @@ for (int i{1}; i < 10; ++i) {
 }
 ```
 
-This loop will sum the numbers from `1` to `9` (including `9`). 
+This loop will sum the numbers from `1` to `9` (including `9`).
 
 ## Break and Continue
 

concepts/loops/introduction.md

@@ -63,7 +63,7 @@ for (int i{1}; i < 10; ++i) {
 }
 ```
 
-This loop will sum the numbers from `1` to `9` (including `9`). 
+This loop will sum the numbers from `1` to `9` (including `9`).
 
 ## Break and Continue
 

concepts/loops/links.json

@@ -7,4 +7,4 @@
         "url": "https://en.cppreference.com/w/cpp/language/while",
         "description": "C++ reference on while loops"
     }
-]
+]

concepts/namespaces/about.md

@@ -44,4 +44,4 @@ namespace o = my_other_ns;
 
 int also_my_result{m::foo() + o::foo() * m::my_inner_ns::baz()};
 ```
-~~~~
+~~~~

concepts/namespaces/links.json

@@ -3,4 +3,4 @@
         "url": "https://en.cppreference.com/w/cpp/language/namespace",
         "description": "C++ reference on namespaces"
     }
-]
+]