this post was submitted on 19 Dec 2024
7 points (76.9% liked)

Advent Of Code

981 readers
21 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

Relevant Communities

Relevant Links

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
 

Day 19 - Linen Layout

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://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 6 days ago (1 children)

Rust

Pretty similar to the other rust answer. This definitely requires

spoilermemoization
of some form, but when done right, is very performant. 122ms for both.

#[cfg(test)]
mod tests {
    use std::collections::HashMap;

    fn count_solutions(
        design: &str,
        patterns: &[&str],
        seen_designs: &mut HashMap<String, i64>,
    ) -> i64 {
        if design.is_empty() {
            return 1;
        }
        if let Some(s) = seen_designs.get(design) {
            return *s;
        }
        let mut count = 0;
        for pattern in patterns {
            if design.starts_with(pattern) {
                count += count_solutions(&design[pattern.len()..], patterns, seen_designs);
            }
        }
        seen_designs.insert(design.to_string(), count);
        count
    }

    #[test]
    fn day19_both_test() {
        let input = std::fs::read_to_string("src/input/day_19.txt").unwrap();
        let parts = input.split_once("\n\n").unwrap();
        let patterns = parts.0.split(", ").collect::<Vec<&str>>();
        let designs = parts.1.split('\n').collect::<Vec<&str>>();

        let mut count = 0;
        let mut total = 0;
        let mut seen_designs = HashMap::new();
        for design in designs {
            let shortlist = patterns
                .iter()
                .filter_map(|p| {
                    if design.contains(p) {
                        return Some(*p);
                    }
                    None
                })
                .collect::<Vec<&str>>();
            let sol_count = count_solutions(design, &shortlist, &mut seen_designs);
            total += sol_count;
            count += (sol_count != 0) as usize;
        }
        println!("{}", count);
        println!("{}", total);
    }
}
[โ€“] [email protected] 2 points 6 days ago (1 children)

I don't know much about Rust but I assume the HashMap<String, i64> requires hashing on insertion and lookup, right? I realized that, for every design, all the strings you'll see are substrings of that design from different starting positions, so I made my lookup table int pos -> int count. The table is reset after every design.

[โ€“] [email protected] 2 points 6 days ago* (last edited 6 days ago) (1 children)

That does mean that if two or more strings end with the same substring, you'd recalculate those substrings? Would be a faster lookup cost though, clever.

My code ran in 120ms, so its pretty damn fast as is, especially compared to the non-memoised version

edit: Tried the array of lengths method, shaved about 20ms off. Not bad, but probably not my main issue either

[โ€“] [email protected] 3 points 6 days ago (1 children)

That does mean that if two or more strings end with the same substring, youโ€™d recalculate those substrings?

I hadn't really considered that, but yes. I'm inclined to think that replacing hash table lookups with plain array indexing (which this allows) outweighs that downside but I'm not sure. Indeed 120ms is pretty damn fast!

[โ€“] [email protected] 1 points 6 days ago (1 children)

It saved me 20ms, and given your using C, saved you dealing with uthash or similar, so probably worth it.

The hashmap is probably a more generic solution though

[โ€“] [email protected] 2 points 5 days ago

Certainly more generic and less prone to user error too. Indeed dealing with hash maps or any advanced data structure is a pain with C, this is where generics or templates really shine, especially if you have control over lifetime aspects as you do with C++ or Rust (e.g. moves, lvalue references, constness, etc).