❄️ - 2023 DAY 3 SOLUTIONS -❄️
❄️ - 2023 DAY 3 SOLUTIONS -❄️
Day 3: Gear Ratios
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)
- Code block support is not fully rolled out yet but likely will be in the middle of the event. Try to share solutions as both code blocks and using something such as https://topaz.github.io/paste/ or pastebin (code blocks to future proof it for when 0.19 comes out and since code blocks currently function in some apps and some instances as well if they are running a 0.19 beta)
FAQ
- What is this?: Here is a post with a large amount of details: https://programming.dev/post/6637268
- 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
🔒This post will be unlocked when there is a decent amount of submissions on the leaderboard to avoid cheating for top spots
🔓 Edit: Post has been unlocked after 11 minutes
You're viewing a single thread.
Did this in Odin
Here's a tip: if you are using a language / standard library that doesn't have a set, you can mimic it with a map from your key to a nullary (in this case an empty struct)
package day3 import "core:fmt" import "core:strings" import "core:unicode" import "core:strconv" flood_get_num :: proc(s: string, i: int) -> (parsed: int, pos: int) { if !unicode.is_digit(rune(s[i])) do return -99999, -1 pos = strings.last_index_proc(s[:i+1], proc(r:rune)->bool{return !unicode.is_digit(r)}) pos += 1 ok: bool parsed, ok = strconv.parse_int(s[pos:]) return parsed, pos } p1 :: proc(input: []string) { // wow what a gnarly type foundNumSet := make(map[[2]int]struct{}) defer delete(foundNumSet) total := 0 for y in 0..Here’s a tip: if you are using a language / standard library that doesn’t have a map,
Probably meant to write 'a set'? Good trick though.
Oh yeah, I misspoke, gonna edit.
hmm, my code keeps getting truncated at
for y in .., anyone have any idea why? Maybe the "<" right after that confuses a parser somewhere?Lemmy doesn't handle certain characters well currently such as left angle brackets and ampersands due to some sanitization in the back end to stop scripting attacks