Sha256: 41fa087f83bb2bbe54d076b1f1df1133732c8972a78e4f3c3edf34ec625a9a48
Contents?: true
Size: 1.65 KB
Versions: 109
Compression:
Stored size: 1.65 KB
Contents
# Meetup Calculate the date of meetups. Typically meetups happen on the same day of the week. In this exercise, you will take a description of a meetup date, and return the actual meetup date. Examples of general descriptions are: - the first Monday of January 2017 - the third Tuesday of January 2017 - the Wednesteenth of January 2017 - the last Thursday of January 2017 Note that "Monteenth", "Tuesteenth", etc are all made up words. There was a meetup whose members realized that there are exactly 7 numbered days in a month that end in '-teenth'. Therefore, one is guaranteed that each day of the week (Monday, Tuesday, ...) will have exactly one date that is named with '-teenth' in every month. Given examples of a meetup dates, each containing a month, day, year, and descriptor (first, second, teenth, etc), calculate the date of the actual meetup. For example, if given "First Monday of January 2017", the correct meetup date is 2017/1/2 The Scala exercises assume an SBT project scheme. The exercise solution source should be placed within the exercise directory/src/main/scala. The exercise unit tests can be found within the exercise directory/src/test/scala. To run the tests simply run the command `sbt test` in the exercise directory. For more detailed info about the Scala track see the [help page](http://exercism.io/languages/scala). ## Source Jeremy Hinegardner mentioned a Boulder meetup that happens on the Wednesteenth of every month [https://twitter.com/copiousfreetime](https://twitter.com/copiousfreetime) ## Submitting Incomplete Solutions It's possible to submit an incomplete solution so you can see how others have completed the exercise.
Version data entries
109 entries across 109 versions & 1 rubygems