Skip to content

java: add solutions for year 2016, day 10 #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 6, 2020
Merged

java: add solutions for year 2016, day 10 #100

merged 3 commits into from
Jan 6, 2020

Conversation

saser
Copy link
Owner

@saser saser commented Jan 6, 2020

From this puzzle I found out how annoying it was to implement queue-based algorithms like Dijkstra's, having to specify an entirely new class for the elements of the queue. One can probably do some hack by using Object arrays and stuff, but I would rather not do that. Perhaps I can find a more convenient way in the future.

Anyhow, this puzzle was fairly fun (I love graph-based puzzles) and I am happy with my solution (and that my solution runs in about 250 microseconds each for part 1 and part 2).

saser added 2 commits January 7, 2020 00:13
I'm not entirely sure this answer is deterministic, since we are using
Hash* collections, although the test continuously passes.
@saser saser merged commit 5873c7e into master Jan 6, 2020
@saser saser deleted the java/2016/10 branch January 6, 2020 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant