Technically simple but designed to catch out the users of, ahem, more academic languages! Rust should offer good performance of course. Optimised build runs both parts in about 5 seconds.
use std::collections::HashMap; type Turn = usize; type Number = i64; struct NumberGame { last_turns: HashMap<Number, Turn>, prev_turns: HashMap<Number, Turn>, starting_numbers: Vec<Number>, next_turn: Turn, last_spoken: Number } impl NumberGame { fn new(starting_numbers: &[Number]) -> Self { NumberGame { last_turns: HashMap::new(), prev_turns: HashMap::new(), starting_numbers: starting_numbers.iter().cloned().collect(), next_turn: 0, last_spoken: 0 } } } impl Iterator for NumberGame { type Item = Number; fn next(&mut self) -> Option<Number> { let next_number = if self.next_turn < self.starting_numbers.len() { self.starting_numbers[self.next_turn] } else { let last = self.last_turns.get(&self.last_spoken).unwrap(); match self.prev_turns.get(&self.last_spoken) { None => 0, Some(prev) => (last - prev) as Number } }; if let Some(prev) = self.last_turns.get(&next_number) { self.prev_turns.insert(next_number, *prev); } self.last_turns.insert(next_number, self.next_turn); self.last_spoken = next_number; self.next_turn += 1; Some(next_number) } } fn number_spoken_at_index(starting_numbers: &[Number], target_index: Turn) -> Number { NumberGame::new(starting_numbers) .skip(target_index - 1) .next() .unwrap() } fn part1(starting_numbers: &[Number]) -> Number { number_spoken_at_index(starting_numbers, 2020) } fn part2(starting_numbers: &[Number]) -> Number { number_spoken_at_index(starting_numbers, 30000000) } fn main() { let input = [15,5,1,4,7,0]; println!("part 1 {}", part1(&input)); println!("part 2 {}", part2(&input)); } #[cfg(test)] mod tests { use super::*; #[test] fn test_number_spoken_at_index() { assert_eq!(number_spoken_at_index(&[0,3,6], 10), 0); assert_eq!(number_spoken_at_index(&[0,3,6], 30000000), 175594); } }
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Technically simple but designed to catch out the users of, ahem, more academic languages! Rust should offer good performance of course. Optimised build runs both parts in about 5 seconds.