Advent Of Code

982 readers

92 users here now

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.

AoC 2024

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

Rules/Guidelines

Follow the programming.dev instance rules
Keep all content related to advent of code in some way
If what youre posting relates to a day, put in brackets the year and then day number in front of the post title (e.g. [2024 Day 10])
When an event is running, keep solutions in the solution megathread to avoid the community getting spammed with posts

Relevant Communities

Relevant Links

Advent of Code Homepage

Credits

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

console.log('Hello World')

founded 1 year ago

MODERATORS

[email protected]

🦌 - 2024 DAY 2 SOLUTIONS -🦌 (programming.dev)

submitted 3 weeks ago by [email protected] to c/[email protected]

57 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 3 weeks ago

J

There is probably a way to write this more point-free. You can definitely see here the friction involved in the way J wants to regard lists as arrays: short rows of the input matrix are zero padded, so you have to snip off the padding before you process each row, and that means you can't lift some of the operations back up to the parent matrix because it will re-introduce the padding as it reshapes the result; this accounts for a lot of the "1 everywhere (you can interpret v"1 as "force the verb v to operate on rank 1 subarrays of the argument").

data_file_name =: '2.data'
data =: > 0 ". each cutopen toJ fread data_file_name

NB. {. take, i. index of; this removes trailing zeros
remove_padding =: {.~ i.&amp;0

NB. }. behead, }: curtail; this computes successive differences
diff =: }. - }:

NB. a b in_range y == a &lt;: y &lt;: b
in_range =: 4 : '(((0 { x) &amp; &lt;:) * (&lt;: &amp; (1 { x))) y'

NB. a row is safe if either all successive differences are in [1..3] or all in [_3.._1]
NB. +. or
ranges =: 2 2 $ 1 3 _3 _1
row_safe =: (+./"1) @: (*/"1) @: (ranges &amp; (in_range"1 _)) @: diff @: remove_padding

result1 =: +/ safe"1 data

NB. x delete y is y without the xth element
delete =: 4 : '(x {. y) , ((>: x) }. y)'"0 _
modified_row =: 3 : 'y , (i.#y) delete y'

modified_row_safe =: 3 : '+./"1 row_safe"1 modified_row"1 y'
result2 =: +/ modified_row_safe data