diff --git a/.github/readme/cover.png b/.github/readme/cover.png deleted file mode 100644 index bb6ca6f..0000000 Binary files a/.github/readme/cover.png and /dev/null differ diff --git a/.github/template-cleanup/README.md b/.github/template-cleanup/README.md deleted file mode 100644 index fc628aa..0000000 --- a/.github/template-cleanup/README.md +++ /dev/null @@ -1,25 +0,0 @@ -# %NAME% - -Welcome to the Advent of Code[^aoc] Kotlin project created by [%ACTOR%][github] using the [Advent of Code Kotlin Template][template] delivered by JetBrains. - -In this repository, %ACTOR% is about to provide solutions for the puzzles using [Kotlin][kotlin] language. - -If you're stuck with Kotlin-specific questions or anything related to this template, check out the following resources: - -- [Kotlin docs][docs] -- [Kotlin Slack][slack] -- Template [issue tracker][issues] - - -[^aoc]: - [Advent of Code][aoc] – An annual event of Christmas-oriented programming challenges started December 2015. - Every year since then, beginning on the first day of December, a programming puzzle is published every day for twenty-four days. - You can solve the puzzle and provide an answer using the language of your choice. - -[aoc]: https://adventofcode.com -[docs]: https://kotlinlang.org/docs/home.html -[github]: https://github.com/%ACTOR% -[issues]: https://github.com/kotlin-hands-on/advent-of-code-kotlin-template/issues -[kotlin]: https://kotlinlang.org -[slack]: https://surveys.jetbrains.com/s3/kotlin-slack-sign-up -[template]: https://github.com/kotlin-hands-on/advent-of-code-kotlin-template diff --git a/.github/template-cleanup/settings.gradle.kts b/.github/template-cleanup/settings.gradle.kts deleted file mode 100644 index 34ec91d..0000000 --- a/.github/template-cleanup/settings.gradle.kts +++ /dev/null @@ -1 +0,0 @@ -rootProject.name = "%NAME%" diff --git a/.github/workflows/template-cleanup.yml b/.github/workflows/template-cleanup.yml deleted file mode 100644 index e88e9d1..0000000 --- a/.github/workflows/template-cleanup.yml +++ /dev/null @@ -1,69 +0,0 @@ -# GitHub Actions Workflow responsible for cleaning up the Advent of Code Kotlin Template repository from -# the template-specific files and configurations. This workflow is supposed to be triggered automatically -# when a new template-based repository has been created. - -name: Template Cleanup -on: - push: - branches: - - main - -jobs: - - # Run cleaning process only if workflow is triggered by the .../advent-of-code-kotlin-template repository. - template-cleanup: - name: Template Cleanup - runs-on: ubuntu-latest - if: github.event.repository.name != 'advent-of-code-kotlin-template' - steps: - - # Check out current repository - - name: Fetch Sources - uses: actions/checkout@v2.4.0 - - # Cleanup project - - name: Cleanup - run: | - export LC_CTYPE=C - export LANG=C - - # Prepare variables - NAME="${GITHUB_REPOSITORY##*/}" - ACTOR=$(echo $GITHUB_ACTOR | tr '[:upper:]' '[:lower:]') - SAFE_NAME=$(echo $NAME | sed 's/[^a-zA-Z0-9]//g' | tr '[:upper:]' '[:lower:]') - SAFE_ACTOR=$(echo $ACTOR | sed 's/[^a-zA-Z0-9]//g' | tr '[:upper:]' '[:lower:]') - GROUP="com.github.$SAFE_ACTOR.$SAFE_NAME" - - # Replace placeholders in the template-cleanup files - sed -i "s/%ACTOR%/$ACTOR/g" .github/template-cleanup/* - sed -i "s/%NAME%/$NAME/g" .github/template-cleanup/* - sed -i "s/%REPOSITORY%/${GITHUB_REPOSITORY/\//\\/}/g" .github/template-cleanup/* - sed -i "s/%GROUP%/$GROUP/g" .github/template-cleanup/* - - # Move content - cp -R .github/template-cleanup/* . - - # Cleanup - rm -rf \ - .github/readme \ - .github/template-cleanup \ - .github/workflows/template-cleanup.yml \ - LICENSE - - # Remove leftover empty directories - find . -type d -empty -delete - - # Commit modified files - - name: Commit files - run: | - git config --local user.email "action@github.com" - git config --local user.name "GitHub Action" - git add . - git commit -m "Template cleanup" - - # Push changes - - name: Push changes - uses: ad-m/github-push-action@master - with: - branch: main - github_token: ${{ secrets.GITHUB_TOKEN }} diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 261eeb9..0000000 --- a/LICENSE +++ /dev/null @@ -1,201 +0,0 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. diff --git a/README.md b/README.md index 172f5bc..4f85350 100644 --- a/README.md +++ b/README.md @@ -1,126 +1,25 @@ -# Advent of Code Kotlin Template +# advent-of-code-2021 -[Advent of Code][aoc] – an annual event in December since 2015. -Every year since then, with the first day of December, a programming puzzles contest is published every day for twenty-four days. -A set of Christmas-oriented challenges provide any input you have to use to answer using the language of your choice. -We offer you a template prepared to use with [Kotlin][kotlin] language within this repository. +Welcome to the Advent of Code[^aoc] Kotlin project created by [mfocko][github] using the [Advent of Code Kotlin Template][template] delivered by JetBrains. -![][file:cover] +In this repository, mfocko is about to provide solutions for the puzzles using [Kotlin][kotlin] language. -## Workflow -**Advent of Code Kotlin Template** is a particular type of GitHub repository that lets you speed up the setup phase and start writing your AoC solutions immediately. - -The general idea is straightforward – to create a new project based on this template, you need to log in to your GitHub account and use the **Use this template** green button. -And remember – **do not fork it!** - -After creating a new project based on this template in your account, a dedicated GitHub Actions workflow will start and clean up the code from redundant files. -It will also personalize code to use your username and project name in namespaces and Gradle properties. -How cool is that? - -Right after the [@actions-user][actions-user] actor pushes the second commit to your repository, you're ready to clone it within the IntelliJ IDEA. - -From now, everything's in your hands! -Join the [Advent of Code][aoc] contest, solve the Day O1 as soon as it is published. - -For the following days, copy the `Day01.kt` solution file and increment the day number. - -> Remember to join the Kotlin contest! -> -> To do that, edit your project's _About_ section with ⚙️ icon and add the `aoc-2021-in-kotlin` topic to your project. -> -> **We will find your repository and count you in our giveaway.** - -## Content - -After you create a new project based on the current template repository using the **Use this template** button, a bare minimal scaffold will appear in your GitHub account with the following structure: - -``` -. -├── README.md README file -├── build.gradle.kts Gradle configuration created with Kotlin DSL -├── gradle -│ └── wrapper Gradle Wrapper -├── gradle.properties Gradle configuration properties -├── gradlew *nix Gradle Wrapper script -├── gradlew.bat Windows Gradle Wrapper script -├── settings.gradle.kts Gradle project settings -└── src - ├── 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 checks - └── Utils.kt A set of utility methods shared across your days -``` - -> Note: All task input files are excluded from the repository with `.gitignore` – we should not post them publicly, as Eric Wastl asks for: [Tweet](https://twitter.com/ericwastl/status/1465805354214830081). - -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: - -```kotlin -fun main() { - fun part1(input: List): Int { - return input.size - } - - val input = readInput("Day01") - println(part1(input)) -} -``` - -The [`Utils.kt`][file:utils] file also contains the `String.md5()` method for generating MD5 hash 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 check against the output, like: - -```kotlin -fun main() { - // ... - - val testInput = readInput("Day01_test") - check(part1(testInput) == 13) -} -``` - -The current approach of providing both `part1` and `part2` solutions within the single `Day##.kt` file may sometimes bring a disadvantage due to the first solution calculation when we expect to work on the second part only. -With simple cases that don't consume too much of your time and resources that can be almost unnoticeable, but when solution takes seconds, it is worth considering breaking daily solution into two separated pieces, like `Day07_part1.kt` and `Day07_part2.kt`. - -The final result of your algorithm will be printed on the screen so that you can pass it to the Advent of Code website. - -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 main() { - fun part1(input: List): Int { - return 0 - } - - fun part2(input: List): Int { - return 0 - } - - val input = readInput("Day02") - println(part1(input)) - println(part2(input)) -} -``` - -## Getting help - -If you stuck with Kotlin-specific questions or anything related to this template, check out the following resources: +If you're stuck with Kotlin-specific questions or anything related to this template, check out the following resources: - [Kotlin docs][docs] - [Kotlin Slack][slack] - Template [issue tracker][issues] -[actions-user]: https://github.com/actions-user +[^aoc]: + [Advent of Code][aoc] – An annual event of Christmas-oriented programming challenges started December 2015. + Every year since then, beginning on the first day of December, a programming puzzle is published every day for twenty-four days. + You can solve the puzzle and provide an answer using the language of your choice. + [aoc]: https://adventofcode.com [docs]: https://kotlinlang.org/docs/home.html +[github]: https://github.com/mfocko [issues]: https://github.com/kotlin-hands-on/advent-of-code-kotlin-template/issues -[kiss]: https://en.wikipedia.org/wiki/KISS_principle [kotlin]: https://kotlinlang.org [slack]: https://surveys.jetbrains.com/s3/kotlin-slack-sign-up -[file:cover]: .github/readme/cover.png -[file:utils]: src/Utils.kt +[template]: https://github.com/kotlin-hands-on/advent-of-code-kotlin-template diff --git a/settings.gradle.kts b/settings.gradle.kts index 46ec124..440a565 100644 --- a/settings.gradle.kts +++ b/settings.gradle.kts @@ -1 +1 @@ -rootProject.name = "Advent of Code Kotlin Template" +rootProject.name = "advent-of-code-2021"