Day 2: Red-Nosed Reports
Megathread guidelines
- Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
- You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://blocks.programming.dev if you prefer sending it through a URL
FAQ
- What is this?: Here is a post with a large amount of details: https://programming.dev/post/22323136
- Where do I participate?: https://adventofcode.com/
- Is there a leaderboard for the community?: We have a programming.dev leaderboard with the info on how to join in this post: https://programming.dev/post/6631465
Haskell
This was quite fun! I got a bit distracted trying to rewrite safe
in point-free style, but I think this version is the most readable. Thereβs probably a more monadic way of writing lessOne
as well, but I canβt immediately see it.
safe xs = any gradual [diffs, negate <$> diffs]
where
diffs = zipWith (-) (drop 1 xs) xs
gradual = all (`elem` [1 .. 3])
lessOne [] = []
lessOne (x : xs) = xs : map (x :) (lessOne xs)
main = do
input :: [[Int]] <- map (map read . words) . lines <$> readFile "input02"
print . length $ filter safe input
print . length $ filter (any safe . lessOne) input
Love to see your haskell solutions!
I am so far very amazed with the compactness of your solutions, your lessOne
is very much mind-Bending.
I have never used or seen <$>
before, is it a monadic $
?
Also I canβt seem to find your logic for this safety condition: The levels are either all increasing or all decreasing
, did you figure that it wasnβt necessary?
For the last point, it isnβt needed since the differences between elements should be all positive or all negative for the report to be safe. This is tested with the combination of negate
and gradual
.
I am also enjoying these Haskell solutions. Iβm still learning the language, so itβs been cool to compare my solution with these and grow my understanding of Haskell.
Thanks! The other two posters already answered your questions, I think :)
Haskell makes it really easy to build complex operations out of simple functional building blocks, skipping a lot of boilerplate needed in some other languages. I find the compactness easier to read, but I realize that not everyone would agree.
BTW, Iβm a relative Haskell newbie. Iβm sure more experienced folks could come up with even more interesting solutions!
Uiua
Uiua is still developing very quickly, and this code uses the experimental tuples
function, hence the initial directive.
# Experimental!
"7 6 4 2 1\n1 2 7 8 9\n9 7 6 2 1\n1 3 2 4 5\n8 6 4 4 1\n1 3 6 7 9"
β(βββΈβ @\s)βΈβ @\n # Partition at \n, then at space, parse ints.
IsSorted β +β(βββ.|ββ.) # Compare with sorted array.
IsSmall β /ΓΓβ(>0|<4)β΅βΒ―1-β»1. # Copy offset by 1, check diffs.
IsSafe β ΓβIsSmall IsSorted # Safe if Small steps and Ordered.
IsSafer β Β±/+β‘IsSafe β§
<-1⧻. # Choose 4 from 5, check again.
&p/+β‘IsSafe . # Part1 : Is each row safe?
&p/+β‘(Β±+βIsSafe IsSafer) # Part2 : Is it safe or safer?
How do you write this, not conceptually but physically. Do you have a char picker open at all times?
Haha, you can do it that way, in fact the online Uiua Pad editor has all the operators listed along the top.
But all the operators have ascii names, so you can type e.g.
IsSmall = reduce mul mul fork(>0|<4) abs drop neg 1 - rot 1 dup
and the formatter will reduce that to
IsSmall β /ΓΓβ(>0|<4)β΅βΒ―1-β»1.
whenever you save or execute code.
That works in the Pad, and you can enable similar functionality in other editors.
This looks so alien! Does it work with the full set? The comment says 5, choose 4, but I guess itβs written as n, choose n-1?
Yes, it should do. I do run the solutions against the live data, but sometimes tweak the solutions afterwards, so canβt always guarantee them :-). I left the comment as 5 choose 4 as it felt clearer in the context of the test data.
It does still feel very alien at times, but I do love being able to think about how to adopt a more arrays-based approach to solving these problems.
C
First went through the input in one pass, number by number, but unfortunately that wouldnβt fly for part 2.
Code
#include "common.h"
static int
issafe(int *lvs, int n, int skip)
{
int safe=1, asc=0,prev=0, ns=0,i;
for (i=0; safe && i<n; i++) {
if (i == skip)
{ ns = 1; continue; }
if (i-ns > 0)
safe = safe && lvs[i] != prev &&
lvs[i] > prev-4 && lvs[i] < prev+4;
if (i-ns == 1)
asc = lvs[i] > prev;
if (i-ns > 1)
safe = safe && (lvs[i] > prev) == asc;
prev = lvs[i];
}
return safe;
}
int
main(int argc, const char **argv)
{
char buf[64], *rest, *tok;
int p1=0,p2=0, lvs[16],n=0, i;
if (argc > 1)
DISCARD(freopen(argv[1], "r", stdin));
while ((rest = fgets(buf, sizeof(buf), stdin))) {
for (n=0; (tok = strsep(&rest, " ")); n++) {
assert(n < (int)LEN(lvs));
lvs[n] = (int)strtol(tok, NULL, 10);
}
for (i=-1; i<n; i++)
if (issafe(lvs, n, i))
{ p1 += i == -1; p2++; break; }
}
printf("02: %d %d\n", p1, p2);
}
What is this coding style? The function type, name and open brace placement made me think GNU at first, but the code in the body doesnβt look like GCS at all.
Rust
The function is_sorted_by on Iterators turned out helpful for compactly finding if a report is safe. In part 2 I simply tried the same with each element removed, since all reports are very short.
fn parse(input: String) -> Vec<Vec<i32>> {
input.lines()
.map(|l| l.split_whitespace().map(|w| w.parse().unwrap()).collect())
.collect()
}
fn is_safe(report: impl DoubleEndedIterator<Item=i32> + Clone) -> bool {
let safety = |a: &i32, b: &i32| (1..=3).contains(&(b - a));
report.clone().is_sorted_by(safety) || report.rev().is_sorted_by(safety)
}
fn part1(input: String) {
let reports = parse(input);
let safe = reports.iter().filter(|r| is_safe(r.iter().copied())).count();
println!("{safe}");
}
fn is_safe2(report: &[i32]) -> bool {
(0..report.len()).any(|i| { // Try with each element removed
is_safe(report.iter().enumerate().filter(|(j, _)| *j != i).map(|(_, n)| *n))
})
}
fn part2(input: String) {
let reports = parse(input);
let safe = reports.iter().filter(|r| is_safe2(r)).count();
println!("{safe}");
}
util::aoc_main!();
The is_sorted_
is a really nice approach. I originally tried using that function thinking that |a, b| a > b
or |a, b| a < b
would cut it but it didnβt end up working. I never thought to handle the check for the step being between 1 and 3 in the callback closure for that though.
Haskell
runningDifference :: [Int] -> [Int]
runningDifference (a:[]) = []
runningDifference (a:b:cs) = a - b : (runningDifference (b:cs))
isSafe :: [Int] -> Bool
isSafe ds = (all (> 0) ds || all (< 0) ds) && (all (flip elem [1, 2, 3] . abs) ds)
isSafe2 :: [Int] -> Bool
isSafe2 ds = any (isSafe2') (zip [0..length ds] (cycle [ds]))
isSafe2' (i, ls) = isSafe . runningDifference $ list
where
list = dropIndex i ls
dropIndex _ [] = []
dropIndex 0 (a:as) = dropIndex (-1) as
dropIndex i (a:as) = a : dropIndex (i - 1) as
main = do
c <- getContents
let reports = init . lines $ c
let levels = map (map read . words) reports :: [[Int]]
let differences = map runningDifference levels
let safety = map isSafe differences
let safety2 = map isSafe2 levels
putStrLn . show . length . filter (id) $ safety
putStrLn . show . length . filter (id) $ safety2
return ()
Took me way too long to figure out that I didnβt have to drop one of them differences but the initial Number