Sha256: b81fe461b5ce60a987e7037c68a0d7c4ad695148d41c94837a55b3cfbc5a1692

Contents?: true

Size: 1.98 KB

Versions: 96

Compression:

Stored size: 1.98 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
 

## Running tests

Execute the tests with:

```bash
$ elixir bob_test.exs
```

(Replace `bob_test.exs` with the name of the test file.)

### Pending tests

In the test suites, all but the first test have been skipped.

Once you get a test passing, you can unskip the next one by
commenting out the relevant `@tag :pending` with a `#` symbol.

For example:

```elixir
# @tag :pending
test "shouting" do
  assert Bob.hey("WATCH OUT!") == "Whoa, chill out!"
end
```

Or, you can enable all the tests by commenting out the
`ExUnit.configure` line in the test suite.

```elixir
# ExUnit.configure exclude: :pending, trace: true
```

For more detailed information about the Elixir track, please
see the [help page](http://exercism.io/languages/elixir).

## 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

96 entries across 96 versions & 1 rubygems

Version Path
trackler-2.2.1.91 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.90 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.89 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.88 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.87 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.86 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.85 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.84 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.83 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.82 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.81 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.80 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.79 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.78 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.77 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.76 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.75 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.74 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.73 tracks/elixir/exercises/meetup/README.md
trackler-2.2.1.72 tracks/elixir/exercises/meetup/README.md