apply prettier

.clang-format

@@ -1,16 +1,15 @@
 ---
-  BasedOnStyle: Google
-  AccessModifierOffset: '-2'
-  AlignTrailingComments: 'true'
-  AllowAllParametersOfDeclarationOnNextLine: 'false'
-  AlwaysBreakTemplateDeclarations: 'No'
-  BreakBeforeBraces: Attach
-  ColumnLimit: '100'
-  ConstructorInitializerAllOnOneLineOrOnePerLine: 'true'
-  IncludeBlocks: Regroup
-  IndentPPDirectives: AfterHash
-  IndentWidth: '4'
-  NamespaceIndentation: All
-  BreakBeforeBinaryOperators: All
-  BreakBeforeTernaryOperators: 'true'
-...
+BasedOnStyle: Google
+AccessModifierOffset: "-2"
+AlignTrailingComments: "true"
+AllowAllParametersOfDeclarationOnNextLine: "false"
+AlwaysBreakTemplateDeclarations: "No"
+BreakBeforeBraces: Attach
+ColumnLimit: "100"
+ConstructorInitializerAllOnOneLineOrOnePerLine: "true"
+IncludeBlocks: Regroup
+IndentPPDirectives: AfterHash
+IndentWidth: "4"
+NamespaceIndentation: All
+BreakBeforeBinaryOperators: All
+BreakBeforeTernaryOperators: "true"

README.md

@@ -11,8 +11,7 @@
 
 # recti
 
-
-## Features
+## ✨ Features
 
 - [Modern CMake practices](https://pabloariasal.github.io/2018/02/19/its-time-to-do-cmake-right/)
 - Suited for single header libraries and projects of any scale
@@ -42,7 +41,7 @@
 Eventually, you can remove any unused files, such as the standalone directory or irrelevant github workflows for your project.
 Feel free to replace the License with one suited for your project.
 
-To cleanly separate the library and subproject code, the outer `CMakeList.txt` only defines the library itself while the tests and other subprojects are self-contained in their own directories. 
+To cleanly separate the library and subproject code, the outer `CMakeList.txt` only defines the library itself while the tests and other subprojects are self-contained in their own directories.
 During development it is usually convenient to [build all subprojects at once](#build-everything-at-once).
 
 ### Build and run the standalone target
@@ -64,7 +63,7 @@ cmake -S test -B build/test
 cmake --build build/test
 CTEST_OUTPUT_ON_FAILURE=1 cmake --build build/test --target test
 
-# or simply call the executable: 
+# or simply call the executable:
 ./build/test/RectiTests
 ```
 
@@ -165,7 +164,7 @@ Use this as the main directory for best IDE support.
 > I see you are using `GLOB` to add source files in CMakeLists.txt. Isn't that evil?
 
 Glob is considered bad because any changes to the source file structure [might not be automatically caught](https://cmake.org/cmake/help/latest/command/file.html#filesystem) by CMake's builders and you will need to manually invoke CMake on changes.
-  I personally prefer the `GLOB` solution for its simplicity, but feel free to change it to explicitly listing sources.
+I personally prefer the `GLOB` solution for its simplicity, but feel free to change it to explicitly listing sources.
 
 > I want create additional targets that depend on my library. Should I modify the main CMakeLists to include them?
 

codecov.yaml

@@ -2,4 +2,4 @@ ignore:
   - "test"
 
 comment:
-  require_changes: true
+  require_changes: true

cts.md

@@ -34,10 +34,10 @@ Placement -> STA -> Clock skew scheduling -> CTS -> Routing
 ## Tree topology generation
 
 - Top down (partition)
-    - MMM (Method of means and medians)
-    - BB (balanced bipartition)
+  - MMM (Method of means and medians)
+  - BB (balanced bipartition)
 - Bottom up
-    - Matching based
+  - Matching based
 - Enumerate all binary trees
 - Local refinement
 - Simulated Annealing
@@ -56,6 +56,3 @@ Placement -> STA -> Clock skew scheduling -> CTS -> Routing
 min_dist() - minimum distance
 enlarge()
 intersection()
-
-
-

translation.md

@@ -18,7 +18,7 @@ int main() {
         std::cout << i << std::endl;
     }
     std::cout << i << std::endl;
-    
+
     int j;
     for (j = 0; j < 100; j++) {
         if (j > i) {
@@ -29,7 +29,7 @@ int main() {
     if (j == 100) {
         std::cout << j << std::endl;
     }
-    
+
     return 0;
 }
 ```
@@ -49,4 +49,4 @@ fn main() {
     }
     println!("{}", j);
 }
-```
+```