Add new practice exercise swift-scheduling
#733
Conversation
This file contains 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
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.
This is a brand new exercise that looked interesting so I implemented it.
It's entirely based on dates, so since
Timeis so limited, I had to implement a lot of things myself, which was fun. The tests look a little strange, but I though spelling out the year and stuff would be a lot more useful than checking a Posix integer, it certainly helped me when I was solving it.I am now thinking that we could have a
timeconcept, I think I'll open an issue. It would be pretty short.I also played around with
config.json(part of #630). Maybe it could have been a separate PR...