Lucky tickets - #171
Merged
Merged
Lucky tickets#171
Conversation
Note that the algorithm used in lucky-tickets.go is not the most efficient algorithm, but it is only used to generate the results for the random test cases and typically runs in less than 20 milliseconds. For the longest test case, it took about 2.5 seconds to generate the result on my machine, so I am including the precomputed result for performance. For many languages, a better algorithm will be required to solve the hole within the time constraint.
Collaborator
|
No idea how to solve this one yet, but I'll stick it live and see what people make of it, I presume you have a few solutions prepared ;-) |
Contributor
Author
|
I do have a few. |
Contributor
Author
|
Hmmm. When I go to https://code-golf.io/lucky-tickets, I see a blank page. |
Collaborator
|
Yep, had some fun with the database, the enum is now altered and it works. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the lucky-tickets hole.
Note that the algorithm used in lucky-tickets.go is not the most efficient algorithm, but it is only used to generate the results for the random test cases and typically runs in less than 20 milliseconds. For the longest test case, it took about 2.5 seconds to generate the result on my machine, so I am including the precomputed result for performance. For many languages, a better algorithm will be required to solve the hole within the time constraint.