From f01cdc3d004db9d441fa6fd1f81a2c78c55c9b7c Mon Sep 17 00:00:00 2001 From: Trent Huber Date: Wed, 17 Dec 2025 18:56:56 -0500 Subject: [PATCH] README.md tweaks --- README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 45bf2be..50ebac5 100644 --- a/README.md +++ b/README.md @@ -8,14 +8,14 @@ that day. ## Building -To build a specific file, just `go build` it. The resulting executable expects -to take input from a file named `input.txt` located in the same directory as -you're running the executable in. To specify whether you'd like to process that -input according to the first or second part of that day, you have to pass either -a `1` or a `2` on the command line. Additionally, since each day comes with an -example input used for testing, you can optionally pass `test` at the end of the -command line to take input from `test.txt` instead, which is where I would paste -the test input copied directly from the webpage. +To build any file, just use the `go build` command. The program reads its input +from a file named `input.txt` located in the same directory that you're running +the program in. To specify whether you'd like to process the input according to +the first or second part of that day's challenge, you can either pass a `1` or a +`2` as a command line argument. Each challenge comes with additional smaller +input used for basic testing that can be copied to a file named `test.txt`. +Passing `test` as a command line argument will have the program read input from +`test.txt` instead. If you find this code at all useful, I've included a template, `template.go`, that can be used for any other Advent of Code challenges. -- 2.51.0