refactoring

Author: hsz

README.md

@@ -46,32 +46,34 @@ After you create a new project based on the current template repository using th
     ├── Day01.kt            An empty implementation for the first AoC day
     ├── Day01.txt           An empty file for the Day 01 input data
     ├── Day01_test.txt      An optional Day 01 test input data used for assertion
-    └── utils.kt            A set of utility methods shared across your days
+    └── Utils.kt            A set of utility methods shared across your days
 ```
 
 When the first puzzle appears, go to the `Day01.kt` and for each `part1` and `part2` functions, provide an algorithm implementation using the `input` data loaded from the `src/Day01.txt` file.
 This input data is common for both parts, and you can find it on the bottom of each day on the [Advent of Code][aoc] page.
 
-To read the input data, you can go with the `readInput(name: String)` utility method provided in the [`utils.kt`][file:utils] file, like:
+To read the input data, you can go with the `readInput(name: String)` utility method provided in the [`Utils.kt`][file:utils] file, like:
 
 ```kotlin
-fun part1(input: List<String>): Int {
-    return input.size
-}
-
 fun main() {
+    fun part1(input: List<String>): Int {
+        return input.size
+    }
+
     val input = readInput("Day01")
-    part1(input).also(::println)
+    println(part1(input))
 }
 ```
 
-The [`utils.kt`][file:utils] file also contains the `String.md5()` method for generating MD5 has out of the given string and expects more helper functions for the sake of the [KISS principle][kiss].
+The [`Utils.kt`][file:utils] file also contains the `String.md5()` method for generating MD5 has out of the given string and expects more helper functions for the sake of the [KISS principle][kiss].
 
 Each puzzle describes some test conditions, a small portion of the information that helps check if the produced value for the given test input is valid.
 To handle that case, you can put such an input into a separated file and perform a standard assertion against the output, like:
 
 ```kotlin
 fun main() {
+    // ...
+    
     val testInput = readInput("Day01_test")
     assert(part1(testInput) == 13)
 }
@@ -82,18 +84,18 @@ The final result of your algorithm will be printed on the screen so that you can
 To go with the next day, place the `Day02.txt` file into the `src` with relevant input data and create `Day02.kt` file with a similar code scaffold:
 
 ```kotlin
-fun part1(input: List<String>): Int {
-    return 0
-}
+fun main() {
+    fun part1(input: List<String>): Int {
+        return 0
+    }
 
-fun part2(input: List<String>): Int {
-    return 0
-}
+    fun part2(input: List<String>): Int {
+        return 0
+    }
 
-fun main() {
     val input = readInput("Day02")
-    part1(input).also(::println)
-    part2(input).also(::println)
+    println(part1(input))
+    println(part2(input))
 }
 ```
 
@@ -114,4 +116,4 @@ If you stuck with Kotlin-specific questions or anything related to this template
 [kotlin]: https://kotlinlang.org
 [slack]: https://surveys.jetbrains.com/s3/kotlin-slack-sign-up
 [file:kotlin]: .github/readme/kotlin.svg
-[file:utils]: src/utils.kt
+[file:utils]: src/Utils.kt

src/Day01.kt

@@ -1,17 +1,17 @@
-fun part1(input: List<String>): Int {
-    return input.size
-}
+fun main() {
+    fun part1(input: List<String>): Int {
+        return input.size
+    }
 
-fun part2(input: List<String>): Int {
-    return input.size
-}
+    fun part2(input: List<String>): Int {
+        return input.size
+    }
 
-fun main() {
     // test if implementation meets criteria from the description, like:
     val testInput = readInput("Day01_test")
     assert(part1(testInput) == 1)
 
     val input = readInput("Day01")
-    part1(input).also(::println)
-    part2(input).also(::println)
+    println(part1(input))
+    println(part2(input))
 }