44
๐ฆ - 2024 DAY 2 SOLUTIONS -๐ฆ
(programming.dev)
An unofficial home for the advent of code community on programming.dev!
Advent of Code is an annual Advent calendar of small programming puzzles for a variety of skill sets and skill levels that can be solved in any programming language you like.
Solution Threads
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
1 | ||||||
2 | 3 | 4 | 5 | 6 | 7 | 8 |
9 | 10 | 11 | 12 | 13 | 14 | 15 |
16 | 17 | 18 | 19 | 20 | 21 | 22 |
23 | 24 | 25 |
Icon base by Lorc under CC BY 3.0 with modifications to add a gradient
console.log('Hello World')
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 writinglessOne
as well, but I can't immediately see it.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
andgradual
.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.
<$>
is justfmap
as an infix operator.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!