Merge pull request #3 from michaelavila/add_mit_license

Add MIT license
Add another shouting test

"This Isn't Shouting" shouldn't be considered shouting
Update readme
Fix sigil symbol deprecation warning in v0.12.5+

As of v0.12.5, using % for sigils [is deprecated][1]. The ~ character
should be used instead. This change fixes up various tests and example
files such that they won't throw the deprecation warning.

[1]: https://github.com/elixir-lang/elixir/releases/tag/v0.12.5
Merge pull request #4 from andrewsardone/fix-sigil-deprecation-warning

Fix sigil symbol deprecation warning in v0.12.5+
Fix the order of some test assertions

Several [exercism/xelixir][xel] assertions seem to be flip-flopped, making
their failure message a bit confusing.

The [`assert/1` macro][as] will format failing values in a helpful manner of
comparing actual and expected values. Given a script with a failing test:

```elixir

defmodule Math do
  def add(x, y), do: 0
end

ExUnit.start

defmodule MathTest do
  use ExUnit.Case, async: true

  test "addition works" do
    assert Math.add(1, 1) == 2
  end
end
```

…running `elixir example.exs` produces a helpful failure message:

```
  1) test addition works (MathTest)
     ** (ExUnit.ExpectationError)
                  expected: 0
       to be equal to (==): 2
     at example.exs:11

Finished in 0.02 seconds (0.02s on load, 0.00s on tests)
1 tests, 1 failures
```

The proper form of writing an assertion seems to be:

```elixir
assert actual_value == expected_value
```

Several [exercism/xelixir][xel] tests of swapped the actual and expected
values. For example, if you look at the [the first test of
point_mutations_test.exs][pntmut], the `actual_value` is on the
right-hand-side of the `==`, which produces a confusing failure message:

```
  1) test no difference between empty strands (DNATest)
     ** (ExUnit.ExpectationError)
                  expected: 0
       to be equal to (==): nil
     at point_mutations_test.exs:14
```

The message is not describing the correct failure of
`DNA.hamming_distance/2`, namely, that it's an empty implementation
that's returning `nil` when the caclulation should return 0. Instead,
this message leads the implementer to believe that the function is
returning 0 when `nil` is what one wants.

Switching up the order of these assertions improves the failure messages
and makes it easier to TDD an exercise solution.

[xel]: https://github.com/exercism/xelixir
[as]: http://elixir-lang.org/docs/stable/ExUnit.Assertions.html#assert/1
[pntmut]: https://github.com/exercism/xelixir/blob/8584070f5d8436816c9d7b1480b687947b383bc3/point-mutations/point_mutations_test.exs#L13-L15
Merge pull request #5 from andrewsardone/assertion-order

Fix the order of some test assertions
Fix nomenclature per recent discussions
Introduce proper config file
Delete outdated text config
Add ignore property to config
Add deprecated section to config
Fix a small typo

I believe this was meant to say "imported" and there seems to have been a stray tic mark.
Merge pull request #6 from parkerl/master

Fix a small typo
Partial transition to Elixir 0.13.3
more syntax changes
a few more updates
Run configlet on travis
Fix forth exercise
Fix#	rna-transcription/results
Merge remote-tracking branch 'origin/elixir-0.13.3'

Conflicts:
	etl/etl_test.exs
	forth/example.exs
	grade-school/grade_school_test.exs
	nucleotide-count/nucleotide_count_test.exs
	palindrome-products/palindrome_products_test.exs
	parallel-letter-frequency/example.exs
	pythagorean-triplet/pythagorean_triplet_test.exs
	word-count/example.exs