From 67706808e7edc6e384042e01f6def7d4f52e4d10 Mon Sep 17 00:00:00 2001 From: Erik Tollefsrud Date: Tue, 10 Dec 2024 22:08:58 -0600 Subject: [PATCH 1/2] removes two redundant sentences that are also in the previous paragraph --- README.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/README.md b/README.md index 90183d5..36b69f9 100644 --- a/README.md +++ b/README.md @@ -49,9 +49,6 @@ Then implement part 1 and 2. The `AdventOfCode.swift` file controls which challe 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. From b04ad6af837bfd986700d0fa99f8bfcf7908346f Mon Sep 17 00:00:00 2001 From: Erik Tollefsrud Date: Tue, 10 Dec 2024 22:34:44 -0600 Subject: [PATCH 2/2] adds the word day's for greater clarity of what it's referring to --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 36b69f9..606c954 100644 --- a/README.md +++ b/README.md @@ -45,7 +45,7 @@ let allChallenges: [any AdventDay] = [ ] ``` -Then implement part 1 and 2. The `AdventOfCode.swift` file controls which challenge +Then implement part 1 and 2. The `AdventOfCode.swift` file controls which day's challenge is run with `swift run`. Add your new type to its `allChallenges` array. By default it runs the most recent challenge.