-
Notifications
You must be signed in to change notification settings - Fork 86
Add an Article for Day 17 of 2023 #513
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
Add an Article for Day 17 of 2023 #513
Conversation
36fbcfd
to
5da64ad
Compare
This has a little errata. See #514 |
5da64ad
to
567398e
Compare
567398e
to
069b3f7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A typo in Dijkstra's name. :)
Co-authored-by: Philippus Baalman <[email protected]>
88513ec
to
fb601dd
Compare
1d56e04
to
da00bd7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really nice, thank you! I did some refactoring so that the grid isn't stored as a top level global
Throwing out ideas, we do have this requirement of part1 and part2 not using IO to load the input so its scala.js compatible but perhaps we can add an extra section to each page that covers how to load the input from file that then calls the part1, part2 methods? it could even be tabbed for scala.js/scala native/jvm |
@bishabosha Thanks! I like the change removing global vars with Using Grid. I'll use that pattern in future submissions (and day 23, which I'm writing up now) re: not using IO: Yes! I think that's a great idea. Should we make it work with pastable input in 2024? |
That's what the solver widget is meant to be if I take the time to set them up |
No description provided.