base on Swift starter project for solving Advent of Code challenges. # Advent of Code Swift Starter Project [](https://swift.org) Daily programming puzzles at [Advent of Code](<https://adventofcode.com/>), by [Eric Wastl](<http://was.tl/>). This is a small example starter project for building Advent of Code solutions. ## Usage Swift comes with Xcode, or you can [install it](https://www.swift.org/install/) on a supported macOS, Linux, or Windows platform. If you're using Xcode, you can open this project by choosing File / Open and select the parent directory. If you prefer the command line, you can run the test suite with `swift test`, and run the output with `swift run`. If you're using Visual Studio Code to edit, you might find these Swift extensions useful: - [Swift](https://marketplace.visualstudio.com/items?itemName=swiftlang.swift-vscode) (provides core language edit / debug / test features) - [apple-swift-format](https://marketplace.visualstudio.com/items?itemName=vknabel.vscode-apple-swift-format) (supports the [swift-format](https://github.com/apple/swift-format) package) ## Challenges The challenges assume three files (replace 00 with the day of the challenge). - `Sources/Data/Day00.txt`: the input data provided for the challenge - `Sources/Day00.swift`: the code to solve the challenge - `Tests/Day00.swift`: any unit tests that you want to include To start a new day's challenge, make a copy of these files, updating 00 to the day number. ```diff // Add each new day implementation to this array: let allChallenges: [any AdventDay] = [ - Day00() + Day00(), + Day01(), ] ``` Then implement part 1 and 2. The `AdventOfCode.swift` file controls which challenge is run with `swift run`. Add your new type to its `allChallenges` array. By default it runs the most recent challenge. The `AdventOfCode.swift` file controls which day's challenge is run with `swift run`. By default that runs the most recent challenge in the package. To supply command line arguments use `swift run AdventOfCode`. For example, `swift run -c release AdventOfCode --benchmark 3` builds the binary with full optimizations, and benchmarks the challenge for day 3. ## Linting and Formatting Challenge source code can be linted and formatted automatically using the included dependency on `swift-format`. Lint source code with the following command: ```shell $ swift package lint-source-code ``` Format source code with the following command: ```shell $ swift package format-source-code Plugin ‘Format Source Code’ wants permission to write to the package directory. Stated reason: “This command formats the Swift source files”. Allow this plugin to write to the package directory? (yes/no) ``` To avoid the interactive prompt when formatting source code, use the `--allow-writing-to-package-directory` flag. ```shell $ swift package format-source-code --allow-writing-to-package-directory ``` swift-format will use the built-in default style to lint and format code. A `.swift-format` configuration file can be used to customize the style used, see [Configuration](https://github.com/apple/swift-format/blob/main/Documentation/Configuration.md) for more details. ", Assign "at most 3 tags" to the expected json: {"id":"5540","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"