Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solve Day 02 #4

Merged
merged 4 commits into from
Dec 3, 2020
Merged

Solve Day 02 #4

merged 4 commits into from
Dec 3, 2020

Conversation

manuphatak
Copy link
Owner

@manuphatak manuphatak commented Dec 2, 2020

Day 2: Password Philosophy

Your flight departs in a few days from the coastal airport; the easiest way down to the coast from here is via toboggan .

The shopkeeper at the North Pole Toboggan Rental Shop is having a bad day. "Something's wrong with our computers; we can't log in!" You ask if you can take a look.

Their password database seems to be a little corrupted: some of the passwords wouldn't have been allowed by the Official Toboggan Corporate Policy that was in effect when they were chosen.

To try to debug the problem, they have created a list (your puzzle input) of passwords (according to the corrupted database) and the corporate policy when that password was set .

For example, suppose you have the following list:

1-3 a: abcde
1-3 b: cdefg
2-9 c: ccccccccc

Each line gives the password policy and then the password. The password policy indicates the lowest and highest number of times a given letter must appear for the password to be valid. For example, 1-3 a means that the password must contain a at least 1 time and at most 3 times.

In the above example, _2_ passwords are valid. The middle password, cdefg , is not; it contains no instances of b , but needs at least 1 . The first and third passwords are valid: they contain one a or nine c , both within the limits of their respective policies.

How many passwords are valid according to their policies?

Part Two

While it appears you validated the passwords correctly, they don't seem to be what the Official Toboggan Corporate Authentication System is expecting.

The shopkeeper suddenly realizes that he just accidentally explained the password policy rules from his old job at the sled rental place down the street! The Official Toboggan Corporate Policy actually works a little differently.

Each policy actually describes two positions in the password , where 1 means the first character, 2 means the second character, and so on. (Be careful; Toboggan Corporate Policies have no concept of "index zero"!) Exactly one of these positions must contain the given letter. Other occurrences of the letter are irrelevant for the purposes of policy enforcement.

Given the same example list from above:

  • 1-3 a: _a_ b _c_ de is valid : position 1 contains a and position 3 does not.
  • 1-3 b: _c_ d _e_ fg is invalid : neither position 1 nor position 3 contains b .
  • 2-9 c: c _c_ cccccc _c_ is invalid : both position 2 and position 9 contain c .

How many passwords are valid according to the new interpretation of the policies?

Link

https://adventofcode.com/2020/day/2

@codecov
Copy link

codecov bot commented Dec 2, 2020

Codecov Report

Merging #4 (5ba447d) into main (c801a75) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##              main        #4   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         5    +3     
  Lines            8        23   +15     
=========================================
+ Hits             8        23   +15     
Impacted Files Coverage Δ
src/Day02/Parser.hs 100.00% <100.00%> (ø)
src/Day02/Solution.hs 100.00% <100.00%> (ø)
src/Day02/Utils.hs 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c801a75...5ba447d. Read the comment docs.

@manuphatak manuphatak self-assigned this Dec 3, 2020
@manuphatak manuphatak merged commit 3e02555 into main Dec 3, 2020
@manuphatak manuphatak deleted the day_02 branch December 3, 2020 01:50
@manuphatak manuphatak added the solution A solution to a problem label Dec 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solution A solution to a problem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant