-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Generate boilerplate for 2024/day02
- Loading branch information
1 parent
7aee4c9
commit 03111b3
Showing
6 changed files
with
209 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
// Package day02 contains solution for https://adventofcode.com/2024/day/2 puzzle. | ||
package day02 | ||
|
||
import ( | ||
"io" | ||
|
||
"github.com/obalunenko/advent-of-code/internal/puzzles" | ||
) | ||
|
||
func init() { | ||
puzzles.Register(solution{}) | ||
} | ||
|
||
type solution struct{} | ||
|
||
func (s solution) Year() string { | ||
return puzzles.Year2024.String() | ||
} | ||
|
||
func (s solution) Day() string { | ||
return puzzles.Day02.String() | ||
} | ||
|
||
func (s solution) Part1(input io.Reader) (string, error) { | ||
return "", puzzles.ErrNotImplemented | ||
} | ||
|
||
func (s solution) Part2(input io.Reader) (string, error) { | ||
return "", puzzles.ErrNotImplemented | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,117 @@ | ||
package day02 | ||
|
||
import ( | ||
"errors" | ||
"io" | ||
"path/filepath" | ||
"testing" | ||
"testing/iotest" | ||
|
||
"github.com/stretchr/testify/assert" | ||
|
||
"github.com/obalunenko/advent-of-code/internal/puzzles/common/utils" | ||
) | ||
|
||
func Test_solution_Year(t *testing.T) { | ||
var s solution | ||
|
||
want := "2024" | ||
got := s.Year() | ||
|
||
assert.Equal(t, want, got) | ||
} | ||
|
||
func Test_solution_Day(t *testing.T) { | ||
var s solution | ||
|
||
want := "2" | ||
got := s.Day() | ||
|
||
assert.Equal(t, want, got) | ||
} | ||
|
||
func Test_solution_Part1(t *testing.T) { | ||
var s solution | ||
|
||
type args struct { | ||
input io.Reader | ||
} | ||
|
||
tests := []struct { | ||
name string | ||
args args | ||
want string | ||
wantErr assert.ErrorAssertionFunc | ||
}{ | ||
{ | ||
name: "test example from description", | ||
args: args{ | ||
input: utils.ReaderFromFile(t, filepath.Join("testdata", "input.txt")), | ||
}, | ||
want: "2", | ||
wantErr: assert.NoError, | ||
}, | ||
{ | ||
name: "", | ||
args: args{ | ||
input: iotest.ErrReader(errors.New("custom error")), | ||
}, | ||
want: "", | ||
wantErr: assert.Error, | ||
}, | ||
} | ||
|
||
for _, tt := range tests { | ||
t.Run(tt.name, func(t *testing.T) { | ||
got, err := s.Part1(tt.args.input) | ||
if !tt.wantErr(t, err) { | ||
return | ||
} | ||
|
||
assert.Equal(t, tt.want, got) | ||
}) | ||
} | ||
} | ||
|
||
func Test_solution_Part2(t *testing.T) { | ||
var s solution | ||
|
||
type args struct { | ||
input io.Reader | ||
} | ||
|
||
tests := []struct { | ||
name string | ||
args args | ||
want string | ||
wantErr assert.ErrorAssertionFunc | ||
}{ | ||
{ | ||
name: "", | ||
args: args{ | ||
input: utils.ReaderFromFile(t, filepath.Join("testdata", "input.txt")), | ||
}, | ||
want: "", | ||
wantErr: assert.NoError, | ||
}, | ||
{ | ||
name: "", | ||
args: args{ | ||
input: iotest.ErrReader(errors.New("custom error")), | ||
}, | ||
want: "", | ||
wantErr: assert.Error, | ||
}, | ||
} | ||
|
||
for _, tt := range tests { | ||
t.Run(tt.name, func(t *testing.T) { | ||
got, err := s.Part2(tt.args.input) | ||
if !tt.wantErr(t, err) { | ||
return | ||
} | ||
|
||
assert.Equal(t, tt.want, got) | ||
}) | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
# Puzzle https://adventofcode.com/2024/day/2 | ||
|
||
# --- Day 2: Red-Nosed Reports --- | ||
|
||
## --- Part One --- | ||
|
||
Fortunately, the first location The Historians want to search isn't a long walk from the Chief Historian's office. | ||
|
||
While the Red-Nosed Reindeer nuclear fusion/fission plant appears to contain no sign of the Chief Historian, | ||
the engineers there run up to you as soon as they see you. Apparently, they still talk about the time Rudolph was saved | ||
through molecular synthesis from a single electron. | ||
|
||
They're quick to add that - since you're already here - they'd really appreciate your help analyzing some unusual data | ||
from the Red-Nosed reactor. You turn to check if The Historians are waiting for you, but they seem to have already | ||
divided into groups that are currently searching every corner of the facility. You offer to help with the unusual data. | ||
|
||
The unusual data (your puzzle input) consists of many reports, one report per line. Each report is a list of numbers | ||
called levels that are separated by spaces. For example: | ||
|
||
```text | ||
7 6 4 2 1 | ||
1 2 7 8 9 | ||
9 7 6 2 1 | ||
1 3 2 4 5 | ||
8 6 4 4 1 | ||
1 3 6 7 9 | ||
``` | ||
|
||
This example data contains six reports each containing five levels. | ||
|
||
The engineers are trying to figure out which reports are safe. The Red-Nosed reactor safety systems can only tolerate | ||
levels that are either gradually increasing or gradually decreasing. So, a report only counts as safe if both of the | ||
following are true: | ||
|
||
The levels are either all increasing or all decreasing. | ||
Any two adjacent levels differ by at least one and at most three. | ||
In the example above, the reports can be found safe or unsafe by checking those rules: | ||
|
||
- `7 6 4 2 1`: Safe because the levels are all decreasing by 1 or 2. | ||
- `1 2 7 8 9`: Unsafe because 2 7 is an increase of 5. | ||
- `9 7 6 2 1`: Unsafe because 6 2 is a decrease of 4. | ||
- `1 3 2 4 5`: Unsafe because 1 3 is increasing but 3 2 is decreasing. | ||
- `8 6 4 4 1`: Unsafe because 4 4 is neither an increase or a decrease. | ||
- `1 3 6 7 9`: Safe because the levels are all increasing by 1, 2, or 3. | ||
- | ||
So, in this example, 2 reports are safe. | ||
|
||
Analyze the unusual data from the engineers. How many reports are safe? | ||
|
||
## --- Part Two --- | ||
|
||
<!--- Pass here the description for part two ---> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
7 6 4 2 1 | ||
1 2 7 8 9 | ||
9 7 6 2 1 | ||
1 3 2 4 5 | ||
8 6 4 4 1 | ||
1 3 6 7 9 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters