fix whitespace, format bronze - silver sols

Author: bqi343

.github/PULL_REQUEST_TEMPLATE.md

@@ -2,6 +2,6 @@ _If any of the below don't apply to this Pull Request, mark the checkbox as done
 
 - [ ] I have tested my code.
 - [ ] I have added my solution according to the steps [here](https://usaco.guide/general/adding-solution#steps).
-- [ ] I have followed the code conventions mentioned [here](https://usaco.guide/general/adding-solution/#code-conventions), which include the following: 
+- [ ] I have followed the code conventions mentioned [here](https://usaco.guide/general/adding-solution/#code-conventions), which include the following:
   - I understand that if it is clear that I have not attempted to follow these guidelines (ex. if I have not used tabs to indent), my PR will be closed.
   - If changes are requested, I will re-request the review after making the changes.

.pre-commit-config.yaml

@@ -8,9 +8,15 @@ repos:
     -   id: check-added-large-files
 - repo: local
   hooks:
-    - id: format
-      name: format
+    - id: format-mdx
+      name: format-mdx
       entry: python py/format_code.py
       language: python
       types: [mdx]
       additional_dependencies: [black-with-tabs, clang-format]
+    - id: black-with-tabs
+      name: black-with-tabs
+      entry: black
+      language: python
+      types: [python]
+      additional_dependencies: [black-with-tabs]

CODEOWNERS

@@ -15,4 +15,4 @@
 /content/6_Advanced/ @dustin-miao @dongliu0426
 /solutions/advanced/ @dustin-miao @dongliu0426
 /content/extraProblems.json
-/content/team/ @maggie-j-liu
+/content/team/ @maggie-j-liu

CODE_OF_CONDUCT.md

@@ -73,4 +73,4 @@ available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.ht
 [homepage]: https://www.contributor-covenant.org
 
 For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+https://www.contributor-covenant.org/faq

announcements/2020 Dec.txt

@@ -5,4 +5,4 @@ title: "USACO December Problems Added"
 order: 4
 ---
 
-All problems from the [USACO 2020 December Contest](http://www.usaco.org/index.php?page=dec20results) have been added to the USACO problem table [here](/general/usaco-monthlies).
+All problems from the [USACO 2020 December Contest](http://www.usaco.org/index.php?page=dec20results) have been added to the USACO problem table [here](/general/usaco-monthlies).

announcements/2021 Jan.txt

@@ -5,4 +5,4 @@ title: "USACO January Problems Added"
 order: 4
 ---
 
-All problems from the [USACO 2021 January Contest](http://www.usaco.org/index.php?page=jan21results) have been added to the USACO problem table [here](/general/usaco-monthlies).
+All problems from the [USACO 2021 January Contest](http://www.usaco.org/index.php?page=jan21results) have been added to the USACO problem table [here](/general/usaco-monthlies).

content/1_General/Basic_Debugging.mdx

@@ -189,7 +189,7 @@ submitting to an OJ.
 	</Resource>
 </Resources>
 
-Here's a handy macro that prints the line number (`__LINE__`) and the name of 
+Here's a handy macro that prints the line number (`__LINE__`) and the name of
 the variable (`#v`) in addition to the value of the variable (`v`).
 
 ```cpp
@@ -281,7 +281,7 @@ prog: main.cpp:6: int main(): Assertion `false' failed.
 Command exited with non-zero status 134
 ```
 
-If you want to disable all asserts (say, before submitting) you can add 
+If you want to disable all asserts (say, before submitting) you can add
 `#define NDEBUG` to the start of your program.
 
 ```cpp
@@ -298,8 +298,8 @@ int main() {
 
 ## Stress Testing
 
-If your code is getting WA, one option is to run your buggy solution against 
-another solution that you're relatively confident is correct on randomly 
+If your code is getting WA, one option is to run your buggy solution against
+another solution that you're relatively confident is correct on randomly
 generated data until you find a difference. See the video for details.
 
 <Resources>
@@ -365,7 +365,7 @@ same language.
 Another option is to write three different programs, one for the correct program,
 one for the incorrect program, and one for generating inputs. Then
 you can use the script below to find an input on which the correct and
-incorrect programs differ. If you want to learn how to write these scripts 
+incorrect programs differ. If you want to learn how to write these scripts
 yourself, see [this module](/general/cpp-command#linux).
 
 <LanguageSection>
@@ -557,7 +557,7 @@ fi
 </PySection>
 </LanguageSection>
 
-In essence, a debugger is a tool to "trace code" for you. Using a debugger 
+In essence, a debugger is a tool to "trace code" for you. Using a debugger
 varies from language to language and even from IDE to different
 IDE, so we will only go over the basics of a debugger.
 
@@ -569,7 +569,7 @@ Pros of using a debugger:
 
 Cons of using a debugger:
 
-- It is not much different from just printing the values out at various points 
+- It is not much different from just printing the values out at various points
   in your program.
 - Most competitive programmers do not use debuggers.
 - You cannot see the overall "output" of your program at each stage. For
@@ -589,4 +589,4 @@ be the "Step Over" button that will allow you to move to the next line. Say you
 are at a line with the following code: `dfs(0, -1)`, if you click "step over" the
 debugger will ignore showing you what happens in this function and go to the
 next line. If you click "step in," however, you will enter the function and be
-able to step through that function.
+able to step through that function.

content/1_General/Contests.mdx

@@ -133,7 +133,7 @@ Let me know if there's something else I should try to qualify for!
 	>
 		recently updated
 	</Resource>
-	
+
 	<Resource
 		title="Carrot"
 		url="https://chrome.google.com/webstore/detail/carrot/gakohpplicjdhhfllilcjpfildodfnnn"

content/1_General/Data_Types.mdx

@@ -41,10 +41,10 @@ prerequisites:
 
 <div className="overflow-x-auto">
 
-| _Types_           | `int`                     | `long long`               | `double`                     | `bool`               | `char`            | 
-| ----------------- | ----------------------- | ----------------------- | ------------------------ | -------------------------- | ------------------ | 
-| Description | 32-bit integer          | 64-bit integer          |  Double-precision float     | True/False value   | 8-bit character | 
-| Size (bytes) | 4                       | 8                       | 8                          | 1                  | 1               | 
+| _Types_           | `int`                     | `long long`               | `double`                     | `bool`               | `char`            |
+| ----------------- | ----------------------- | ----------------------- | ------------------------ | -------------------------- | ------------------ |
+| Description | 32-bit integer          | 64-bit integer          |  Double-precision float     | True/False value   | 8-bit character |
+| Size (bytes) | 4                       | 8                       | 8                          | 1                  | 1               |
 | Range       | $-2^{31}$ to $2^{31}-1$ | $-2^{63}$ to $2^{63}-1$ | `-1.7E+308` to `+1.7E+308` | $0$ or $1$ (`true` or `false`) | $-2^7$ to $2^7-1$ |
 
 </div>
@@ -70,9 +70,9 @@ For more primitive data types, check the the first resource in the table above.
 
 <div className="overflow-x-auto">
 
-| _Types_      | `int`                   | `long`                  | `double`                   | `boolean`          | `char`                   | 
-| ------------ | ----------------------- | ----------------------- | -------------------------- | ------------------ | ------------------------ | 
-| Description  | 32-bit integer          | 64-bit integer          | Double-precision float     | True/False value   | 16-bit Unicode character | 
+| _Types_      | `int`                   | `long`                  | `double`                   | `boolean`          | `char`                   |
+| ------------ | ----------------------- | ----------------------- | -------------------------- | ------------------ | ------------------------ |
+| Description  | 32-bit integer          | 64-bit integer          | Double-precision float     | True/False value   | 16-bit Unicode character |
 | Size (bytes) | 4                       | 8                       | 8                          | 1 bit(\*)          | 2                        |
 | Range        | $-2^{31}$ to $2^{31}-1$ | $-2^{63}$ to $2^{63}-1$ | `-1.7E+308` to `+1.7E+308` | true/false         | `\u0000` to `\uffff` ($0-65535$) |
 

content/1_General/Debugging_Checklist.mdx

@@ -29,8 +29,8 @@ most relevant to USACO.
 
 <Info title="Code Snippets">
 
-This module doesn't contain any code. See [Basic 
-Debugging](/general/basic-debugging) and [Debugging C++](/general/debugging-cpp) 
+This module doesn't contain any code. See [Basic
+Debugging](/general/basic-debugging) and [Debugging C++](/general/debugging-cpp)
 for more information.
 
 </Info>
@@ -124,7 +124,7 @@ for more information.
 ## Last Resort
 
 - Rewrite your solution from the start.
-  - Be sure to save a copy of your original solution. It's always possible that 
+  - Be sure to save a copy of your original solution. It's always possible that
     you might introduce more bugs in your new solution.
 
 ## Before Posting on the [USACO Guide Forum](https://forum.usaco.guide/)

content/1_General/Debugging_Cpp.mdx

@@ -9,10 +9,10 @@ prerequisites:
 
 ## Checking for Out of Bounds
 
-Writing to an out of bounds array index is known as 
-[buffer overflow](https://en.wikipedia.org/wiki/Buffer_overflow). C++ may or 
-may not produce a runtime error upon buffer overflow. For example, 
-the following code results in a runtime error on 
+Writing to an out of bounds array index is known as
+[buffer overflow](https://en.wikipedia.org/wiki/Buffer_overflow). C++ may or
+may not produce a runtime error upon buffer overflow. For example,
+the following code results in a runtime error on
 [ide.usaco.guide](https://ide.usaco.guide), but outputs 4 on my computer.
 
 ```cpp
@@ -31,7 +31,7 @@ int main() {
 }
 ```
 
-To ensure that an error is raised when accessing an out of bounds index, 
+To ensure that an error is raised when accessing an out of bounds index,
 you can use
 [vector::at](https://www.cplusplus.com/reference/vector/vector/at) instead of
 [vector::operator[]](https://www.cplusplus.com/reference/vector/vector/operator[])
@@ -66,7 +66,7 @@ terminate called after throwing an instance of 'std::out_of_range'
 <Info title="Line Numbers">
 
 Note that the output above does not contain the line number where the runtime
-error occurred. To output the line number, you can use a debugger such as `gdb` 
+error occurred. To output the line number, you can use a debugger such as `gdb`
 or `lldb`. See the section on [debuggers](#using-the-lldb-debugger) for more information.
 
 </Info>
@@ -166,7 +166,7 @@ In this section and the following one we'll go over options you can add to your
 	>
 		Includes all the options below.
 	</Resource>
-  <Resource 
+  <Resource
     source="GCC"
     title="GCC Warning Options"
     url="https://web.archive.org/web/20221101061037/https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html"
@@ -185,7 +185,7 @@ We give examples for some of these below.
 
 <Info title="For Users of USACO Guide IDE">
 
-You can customize your compilation options in 
+You can customize your compilation options in
 [ide.usaco.guide](https://ide.usaco.guide/).
 
 </Info>
@@ -224,7 +224,7 @@ main.cpp:6:10: warning: ‘x’ is used uninitialized in this function [-Wuninit
 
 ### `-Wextra`
 
-Enables some warning options not enabled by `-Wall`, such as 
+Enables some warning options not enabled by `-Wall`, such as
 `-Wmissing-field-initializers`.
 
 ```cpp
@@ -372,7 +372,7 @@ main.cpp:6:13: runtime error: index 5 out of bounds for type 'int [5]'
 main.cpp:6:13: runtime error: load of address 0x7ffc4efaf2d4 with insufficient space for an object of type 'int'
 0x7ffc4efaf2d4: note: pointer points here
   11 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  f0 15 40 00 00 00 00 00  00 00 00 00 00 00 00 00
-              ^ 
+              ^
 ```
 
 #### Example: Vector Out of Bounds
@@ -396,7 +396,7 @@ Output:
 Command exited with non-zero status 139
 ```
 
-With `-fsanitize=undefined`, a slightly more informative error message is 
+With `-fsanitize=undefined`, a slightly more informative error message is
 produced:
 
 ```
@@ -427,7 +427,7 @@ main.cpp:6:14: runtime error: signed integer overflow: 1073741824 * 2 cannot be
 #### Example: Detecting Multiple Errors
 
 By default, the undefined behavior sanitizer will attempt to continue after
-detecting an error. For example, the following program with 
+detecting an error. For example, the following program with
 `-fsanitize=undefined` produces multiple runtime errors:
 
 ```cpp
@@ -509,7 +509,7 @@ Command exited with non-zero status 1
 
 For more helpful information we should additionally compile with the `-g` flag,
 which generates a file containing debugging information based on the line
-numbering of the program. 
+numbering of the program.
 
 <Spoiler title="Standard Error">
 
@@ -579,7 +579,7 @@ Shadow bytes around the buggy address:
   0x1000750d9870: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 Shadow byte legend (one shadow byte represents 8 application bytes):
   Addressable:           00
-  Partially addressable: 01 02 03 04 05 06 07 
+  Partially addressable: 01 02 03 04 05 06 07
   Heap left redzone:       fa
   Freed heap region:       fd
   Stack left redzone:      f1
@@ -605,7 +605,7 @@ Command exited with non-zero status 1
 
 ### `-D_GLIBCXX_DEBUG`
 
-This enables debug mode, which replaces each STL container with its 
+This enables debug mode, which replaces each STL container with its
 corresponding debug container.
 
 <Resources>
@@ -669,8 +669,8 @@ zsh: abort      ./prog
 </Resources>
 
 Recall the example from [Checking Out of Bounds](#checking-for-out-of-bounds)
-section where the output didn't contain the number of the line where the 
-runtime error occurred. Below, we show how to use `lldb` to output the line 
+section where the output didn't contain the number of the line where the
+runtime error occurred. Below, we show how to use `lldb` to output the line
 number. Assume the C++ source code is named `prog.cpp` and the executable
 is named `prog`.
 
@@ -699,7 +699,7 @@ libsystem_kernel.dylib`__pthread_kill:
 ->  0x7ff80e01300e <+10>: jae    0x7ff80e013018            ; <+20>
     0x7ff80e013010 <+12>: movq   %rax, %rdi
     0x7ff80e013013 <+15>: jmp    0x7ff80e00d1c5            ; cerror_nocancel
-    0x7ff80e013018 <+20>: retq   
+    0x7ff80e013018 <+20>: retq
 Target 0: (prog) stopped.
 (lldb) bt
 * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
@@ -715,15 +715,15 @@ Target 0: (prog) stopped.
     frame #9: 0x0000000100002629 prog`std::vector<int, std::allocator<int> >::at(this=0x00007ff7bfeff3d0, __n=1) at stl_vector.h:1175:16
     frame #10: 0x0000000100002421 prog`main at prog.cpp:10:17
     frame #11: 0x000000010001552e dyld`start + 462
-(lldb) 
+(lldb)
 ```
 
 </Spoiler>
 
 <Info>
 
 As mentioned in [the previous module](/general/basic-debugging?lang=cpp#debuggers),
-there are many more things you can do with debuggers, but they aren't 
+there are many more things you can do with debuggers, but they aren't
 particularly useful for competitive programming.
 
-</Info>
+</Info>

content/1_General/Fast_IO.mdx

@@ -12,7 +12,7 @@ briefly mentions some ways of speeding up I/O:
 
 > For some of the more advanced problems with larger input sizes, competitors may benefit from using fast input/output, to more easily pass within the time limit. For C++ users, you may want to add "ios_base::sync_with_stdio(false); cin.tie(0);" to the top of your main method if you are using cin/cout. For Java users, you may want to use BufferedReader instead of Scanner.
 
-What do these do and how much of a difference do these actually make? We'll use the following 
+What do these do and how much of a difference do these actually make? We'll use the following
 task to benchmark I/O speed:
 
 ## Example Task
@@ -955,4 +955,4 @@ details.
 
 </Warning>
 
-</CPPOnly>
+</CPPOnly>

content/1_General/Intro_CP.mdx

@@ -78,7 +78,7 @@ Here is a task similar to the one that was solved in Kamil's video:
 <FocusProblem problem="general" />
 
 <Info title="Beginners!">
-If you have prior programming experience we encourage you to register a Kattis account and submit a solution. 
+If you have prior programming experience we encourage you to register a Kattis account and submit a solution.
 If not, feel free to skip ahead to the solution.
 </Info>
 

content/1_General/Modules.mdx

@@ -133,7 +133,7 @@ Pay attention to content within warning blocks!
 
 </Warning>
 
-See [Working With MDX](/general/working-mdx) for more information regarding 
+See [Working With MDX](/general/working-mdx) for more information regarding
 custom components.
 
 ## Statuses
@@ -152,6 +152,6 @@ Module (and Resource) Statuses:
  - Not Started - Self-explanatory.
  - Reading - Self-explanatory. Will show up under dashboard active modules.
  - Practicing - Self-explanatory. Will show up under dashboard active modules.
- - Complete - Self-explanatory. 
+ - Complete - Self-explanatory.
  - Skipped - Use for modules that you have skipped and intend to come back to. Will show up under dashboard active modules.
  - Ignored - Use for modules that you have skipped and do not intend to come back to. Will show up under dashboard active modules if enabled in settings.

content/1_General/Working_MDX.mdx

@@ -560,7 +560,7 @@ Java code here
 <PySection />
 </LanguageSection>
 
-If you want to render content for only a single language, it is more convenient 
+If you want to render content for only a single language, it is more convenient
 to use `CPPOnly`, `JavaOnly`, or `PyOnly`:
 
 ````
@@ -691,4 +691,4 @@ C++ code here
 			</Quiz.Explanation>
 		</Quiz.Answer>
 	</Quiz.Question>
-</Quiz>
+</Quiz>

content/1_General/Working_MDX.problems.json

@@ -1,3 +1,3 @@
 {
   "MODULE_ID": "working-mdx"
-}
+}