-
Notifications
You must be signed in to change notification settings - Fork 16
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
Standardize Output #28
Comments
JSON? |
We should probably think about masking the answer to prevent people from Googling the problem and getting an answer immediately. Kind of detracts from the spirit of Project Euler. |
Perhaps a file that is added manually that contains the answers (one per line) and is listed in .gitignore to prevent it from getting shared (or overwritten)? |
I thought about adding a single file with all the answers - because the answers are the same no matter the language - but decided against it because I didn't want to bloat the repo with file I/O functionality when all we need to do is include a number in each working file. But I could be convinced in another direction possibly. I wasn't too worried about people finding the answer in this repo since this in unlikely to become the canonical repo for Project Euler solutions anytime soon. But who knows I guess. Everyone is doing a great job. |
I'm in favor of a single answers file where the answers are (perhaps) Base64 encoded (meaning their values won't be indexable by google, but anyone who wants to cheat could go through the exercise of decoding them). I've already removed all of the answers from the F# examples. |
If we have a common output format for all solutions then parsing or otherwise using the result of a solution attempt will be easier.
The text was updated successfully, but these errors were encountered: