trackler 2.2.1.72 → 2.2.1.73

data/tracks/go/exercises/bob/README.md

@@ -6,6 +6,8 @@ Bob answers 'Sure.' if you ask him a question.
 
 He answers 'Whoa, chill out!' if you yell at him.
 
+He answers 'Calm down, I know what I'm doing!' if you yell a question at him.
+
 He says 'Fine. Be that way!' if you address him without actually saying
 anything.
 

data/tracks/go/exercises/bob/cases_test.go

@@ -1,8 +1,8 @@
 package bob
 
 // Source: exercism/problem-specifications
-// Commit: 65756b1 bob: Fix canonical-data.json formatting
-// Problem Specifications Version: 1.0.0
+// Commit: fef09f6 Bob: Add fifth rule (#1025)
+// Problem Specifications Version: 1.1.0
 
 var testCases = []struct {
 	description string
@@ -52,7 +52,7 @@ var testCases = []struct {
 	{
 		"forceful question",
 		"WHAT THE HELL WERE YOU THINKING?",
-		"Whoa, chill out!",
+		"Calm down, I know what I'm doing!",
 	},
 	{
 		"shouting numbers",

data/tracks/go/exercises/bob/example.go

@@ -8,6 +8,9 @@ func Hey(remark string) string {
 	case silent(remark):
 		return "Fine. Be that way!"
 	case yelling(remark):
+		if asking(remark) {
+			return "Calm down, I know what I'm doing!"
+		}
 		return "Whoa, chill out!"
 	case asking(remark):
 		return "Sure."

data/tracks/go/exercises/book-store/cases_test.go

@@ -1,8 +1,8 @@
 package bookstore
 
 // Source: exercism/problem-specifications
-// Commit: 087ad69 book-store: Add missing trailing zero
-// Problem Specifications Version: 1.0.1
+// Commit: a636903 Update description per @insti comments
+// Problem Specifications Version: 1.1.0
 
 var testCases = []struct {
 	description string
@@ -74,4 +74,9 @@ var testCases = []struct {
 		basket:      []int{1, 1, 2, 2, 3, 3, 4, 4, 5, 5, 1, 2},
 		expected:    75.20,
 	},
+	{
+		description: "Four groups of four are cheaper than two groups each of five and three",
+		basket:      []int{1, 1, 2, 2, 3, 3, 4, 5, 1, 1, 2, 2, 3, 3, 4, 5},
+		expected:    102.40,
+	},
 }

data/tracks/go/exercises/word-count/cases_test.go

@@ -1,7 +1,7 @@
 package wordcount
 
 // Source: exercism/problem-specifications
-// Commit: cd26d49 word-count: Make exercise schema-compliant  (#634)
+// Commit: 8793a05 word-count: Add test for multiple whitespace (#1023)
 // Problem Specifications Version: 1.0.0
 
 var testCases = []struct {
@@ -59,4 +59,9 @@ var testCases = []struct {
 		"Joe can't tell between 'large' and large.",
 		Frequency{"and": 1, "between": 1, "can't": 1, "joe": 1, "large": 2, "tell": 1},
 	},
+	{
+		"multiple spaces not detected as a word",
+		" multiple   whitespaces",
+		Frequency{"multiple": 1, "whitespaces": 1},
+	},
 }

data/tracks/groovy/exercises/linked-list/README.md

@@ -35,7 +35,7 @@ For installation and learning resources, refer to the
 You can run all the tests for an exercise by entering
 
 ```
-$ groovy ./LinkedListSpec.groovy
+$ groovy ./DoubleLinkedListSpec.groovy
 ```
 
 in your terminal.

data/tracks/haskell/.travis.yml

@@ -32,6 +32,7 @@ install:
  - stack --resolver ${RESOLVER} --install-ghc install hlint
 
 script:
+ - "sh ./bin/ensure-readmes-are-updated.sh"
  - |
     set -e
 

data/tracks/haskell/bin/ensure-readmes-are-updated.sh

@@ -0,0 +1,40 @@
+if [ ! -x bin/configlet ]; then
+   echo "Improper configuration; configlet should exist in bin/ when this script is run"
+   echo "Ping a Haskell track maintainer to fix this"
+   exit 1
+fi
+
+if [ ! -d "problem-specifications" ]; then
+   git clone https://github.com/exercism/problem-specifications.git problem-specifications
+fi
+
+newline=$'\n  '
+
+missing_readmes=""
+wrong_readmes=""
+for exercise in $(git diff --name-only master..$(git rev-parse --abbrev-ref HEAD) | grep exercises/ | cut -d'/' -f2 -s | sort -fu); do
+   echo "Checking readme for $exercise"
+   readme_path="exercises/${exercise}/README.md"
+   if [ ! -f $readme_path ]; then
+      missing_readmes="$missing_readmes$newline$exercise"
+   else
+      existing_readme_checksum=$(md5sum $readme_path | cut -d' ' -f1)
+      # generate the new README
+      bin/configlet generate . --only "$exercise" --spec-path "problem-specifications"
+      generated_readme_checksum=$(md5sum $readme_path | cut -d' ' -f1)
+
+      if [ $existing_readme_checksum != $generated_readme_checksum ]; then
+         wrong_readmes="$wrong_readmes$newline$exercise"
+      fi
+   fi
+done
+
+if [ -n "$missing_readmes" ]; then
+  echo "Exercises missing README.md:$missing_readmes"
+fi
+if [ -n "$wrong_readmes" ]; then
+  echo "Exercises with out-of-date README.md:$wrong_readmes"
+fi
+if [ -n "$missing_readmes" -o -n "$wrong_readmes" ]; then
+   exit 1
+fi

data/tracks/haskell/config.json

@@ -31,6 +31,15 @@
       "topics": [
       ]
     },
+    {
+      "uuid": "5bf7612c-427e-484d-bc67-8553fac4f64d",
+      "slug": "rail-fence-cipher",
+      "core": false,
+      "unlocked_by": null,
+      "difficulty": 1,
+      "topics": [
+      ]
+    },
     {
       "uuid": "6cbb7841-9d96-4528-88e3-6e98a450fd7c",
       "slug": "space-age",

data/tracks/haskell/exercises/rail-fence-cipher/README.md

@@ -0,0 +1,119 @@
+# Rail Fence Cipher
+
+Implement encoding and decoding for the rail fence cipher.
+
+The Rail Fence cipher is a form of transposition cipher that gets its name from
+the way in which it's encoded. It was already used by the ancient Greeks.
+
+In the Rail Fence cipher, the message is written downwards on successive "rails"
+of an imaginary fence, then moving up when we get to the bottom (like a zig-zag).
+Finally the message is then read off in rows.
+
+For example, using three "rails" and the message "WE ARE DISCOVERED FLEE AT ONCE",
+the cipherer writes out:
+
+```text
+W . . . E . . . C . . . R . . . L . . . T . . . E
+. E . R . D . S . O . E . E . F . E . A . O . C .
+. . A . . . I . . . V . . . D . . . E . . . N . .
+```
+
+Then reads off:
+
+```text
+WECRLTEERDSOEEFEAOCAIVDEN
+```
+
+To decrypt a message you take the zig-zag shape and fill the ciphertext along the rows.
+
+```text
+? . . . ? . . . ? . . . ? . . . ? . . . ? . . . ?
+. ? . ? . ? . ? . ? . ? . ? . ? . ? . ? . ? . ? .
+. . ? . . . ? . . . ? . . . ? . . . ? . . . ? . .
+```
+
+The first row has seven spots that can be filled with "WECRLTE".
+
+```text
+W . . . E . . . C . . . R . . . L . . . T . . . E
+. ? . ? . ? . ? . ? . ? . ? . ? . ? . ? . ? . ? .
+. . ? . . . ? . . . ? . . . ? . . . ? . . . ? . .
+```
+
+Now the 2nd row takes "ERDSOEEFEAOC".
+
+```text
+W . . . E . . . C . . . R . . . L . . . T . . . E
+. E . R . D . S . O . E . E . F . E . A . O . C .
+. . ? . . . ? . . . ? . . . ? . . . ? . . . ? . .
+```
+
+Leaving "AIVDEN" for the last row.
+
+```text
+W . . . E . . . C . . . R . . . L . . . T . . . E
+. E . R . D . S . O . E . E . F . E . A . O . C .
+. . A . . . I . . . V . . . D . . . E . . . N . .
+```
+
+If you now read along the zig-zag shape you can read the original message.
+
+
+## Getting Started
+
+For installation and learning resources, refer to the
+[exercism help page](http://exercism.io/languages/haskell).
+
+## Running the tests
+
+To run the test suite, execute the following command:
+
+```bash
+stack test
+```
+
+#### If you get an error message like this...
+
+```
+No .cabal file found in directory
+```
+
+You are probably running an old stack version and need
+to upgrade it.
+
+#### Otherwise, if you get an error message like this...
+
+```
+No compiler found, expected minor version match with...
+Try running "stack setup" to install the correct GHC...
+```
+
+Just do as it says and it will download and install
+the correct compiler version:
+
+```bash
+stack setup
+```
+
+## Running *GHCi*
+
+If you want to play with your solution in GHCi, just run the command:
+
+```bash
+stack ghci
+```
+
+## Feedback, Issues, Pull Requests
+
+The [exercism/haskell](https://github.com/exercism/haskell) repository on
+GitHub is the home for all of the Haskell exercises.
+
+If you have feedback about an exercise, or want to help implementing a new
+one, head over there and create an issue.  We'll do our best to help you!
+
+## Source
+
+Wikipedia [https://en.wikipedia.org/wiki/Transposition_cipher#Rail_Fence_cipher](https://en.wikipedia.org/wiki/Transposition_cipher#Rail_Fence_cipher)
+
+## Submitting Incomplete Solutions
+It's possible to submit an incomplete solution so you can see how others have completed the exercise.

data/tracks/haskell/exercises/rail-fence-cipher/examples/success-standard/package.yaml

@@ -0,0 +1,16 @@
+name: rail-fence-cipher
+
+dependencies:
+  - base
+
+library:
+  exposed-modules: RailFenceCipher
+  source-dirs: src
+
+tests:
+  test:
+    main: Tests.hs
+    source-dirs: test
+    dependencies:
+      - rail-fence-cipher
+      - hspec

data/tracks/haskell/exercises/rail-fence-cipher/examples/success-standard/src/RailFenceCipher.hs

@@ -0,0 +1,12 @@
+module RailFenceCipher (encode, decode) where
+
+import Data.List (sortBy)
+import Data.Function (on)
+
+encode :: Int -> [a] -> [a]
+encode n xs = concat [[a | (a, b) <- zip xs c, b == i] | i <- [1..n]]
+  where c = cycle $ [1..n] ++ [n-1,n-2..2]
+
+decode :: Int -> [a] -> [a]
+decode n xs = map snd $ sortBy (compare `on` fst) zippedL
+  where zippedL = zip (encode n [0..length xs - 1]) xs

data/tracks/haskell/exercises/rail-fence-cipher/package.yaml

@@ -0,0 +1,20 @@
+name: rail-fence-cipher
+version: 1.1.0.1
+
+dependencies:
+  - base
+
+library:
+  exposed-modules: RailFenceCipher
+  source-dirs: src
+  dependencies:
+  # - foo       # List here the packages you
+  # - bar       # want to use in your solution.
+
+tests:
+  test:
+    main: Tests.hs
+    source-dirs: test
+    dependencies:
+      - rail-fence-cipher
+      - hspec

data/tracks/haskell/exercises/rail-fence-cipher/src/RailFenceCipher.hs

@@ -0,0 +1,7 @@
+module RailFenceCipher (encode, decode) where
+
+encode :: Int -> String -> String
+encode = error "You need to implement this function!"
+
+decode :: Int -> String -> String
+decode = error "You need to implement this function!"

data/tracks/haskell/exercises/rail-fence-cipher/stack.yaml

@@ -0,0 +1 @@
+resolver: lts-9.11

data/tracks/haskell/exercises/rail-fence-cipher/test/Tests.hs

@@ -0,0 +1,60 @@
+{-# LANGUAGE RecordWildCards #-}
+
+import Data.Foldable     (for_)
+import Test.Hspec        (Spec, describe, it, shouldBe)
+import Test.Hspec.Runner (configFastFail, defaultConfig, hspecWith)
+
+import RailFenceCipher (encode, decode)
+
+main :: IO ()
+main = hspecWith defaultConfig {configFastFail = True} specs
+
+specs :: Spec
+specs = do
+          describe "encode" $ for_ encodeCases testE
+          describe "decode" $ for_ decodeCases testD
+  where
+    testE Case{..} = it description $ encode key text `shouldBe` expected
+    testD Case{..} = it description $ decode key text `shouldBe` expected
+
+data Case = Case { description :: String
+                 , key         :: Int
+                 , text        :: String
+                 , expected    :: String
+                 }
+
+encodeCases :: [Case]
+encodeCases = [ Case { description = "encode with two rails"
+                     , key         = 2
+                     , text        = "XOXOXOXOXOXOXOXOXO"
+                     , expected    = "XXXXXXXXXOOOOOOOOO"
+                     }
+              , Case { description = "encode with three rails"
+                     , key         = 3
+                     , text        = "WEAREDISCOVEREDFLEEATONCE"
+                     , expected    = "WECRLTEERDSOEEFEAOCAIVDEN"
+                     }
+              , Case { description = "encode with ending in the middle"
+                     , key         = 4
+                     , text        = "EXERCISES"
+                     , expected    = "ESXIEECSR"
+                     }
+              ]
+
+decodeCases :: [Case]
+decodeCases = [ Case { description = "decode with three rails"
+                     , key         = 3
+                     , text        = "TEITELHDVLSNHDTISEIIEA"
+                     , expected    = "THEDEVILISINTHEDETAILS"
+                     }
+              , Case { description = "decode with five rails"
+                     , key         = 5
+                     , text        = "EIEXMSMESAORIWSCE"
+                     , expected    = "EXERCISMISAWESOME"
+                     }
+              , Case { description = "decode with six rails"
+                     , key         = 6
+                     , text        = "133714114238148966225439541018335470986172518171757571896261"
+                     , expected    = "112358132134558914423337761098715972584418167651094617711286"
+                     }
+              ]

data/tracks/java/CONTRIBUTING.md

@@ -85,6 +85,7 @@ The `exercises` subdirectory contains all of the problem submodules.
 Each problem/submodule is a subdirectory of the same name as its slug.
 
   * its `build.gradle` names dependencies required to work that problem.
+  * its `README.md` describes the exercise.
 
 Each problem/submodule has three source sets:
 
@@ -152,19 +153,27 @@ Also please make a [dibs pull request](https://github.com/exercism/docs/blob/mas
 
 The Java specific details you need to know about adding an exercise are:
 
-1. Please add an entry to the `exercises` array in `config.json`. You can find details about what should be in that entry [here](https://github.com/exercism/docs/blob/master/language-tracks/configuration/exercises.md).
+* Please add an entry to the `exercises` array in `config.json`. You can find details about what should be in that entry [here](https://github.com/exercism/docs/blob/master/language-tracks/configuration/exercises.md).
 You can also look at other entries in `config.json` as examples and try to mimic them.
 
-2. Please add an entry for your exercise to `settings.gradle`.
+* Please add an entry for your exercise to `settings.gradle`.
 This should just be `include 'exercise-name'`.
 This list is in alphabetical order so please add your exercise so that it maintains this order.
 
-3. Please add an exercise submodule for your exercise.
+* Please add an exercise submodule for your exercise.
 See [The Problem Submodules](#the-problem-submodules) section for what needs to be in this.
-The `build.gradle` file can just be copied from any other exercise submodule.
 See the [POLICIES doc](https://github.com/exercism/java/blob/master/POLICIES.md#starter-implementations) for an explanation of when you need to add a starter implementation.
+The `build.gradle` file can just be copied from any other exercise submodule.
+The `README.md` file can be generated using [configlet](https://github.com/exercism/configlet/releases).
+You can do this by:
+
+  1. Download configlet and put it somewhere in your PATH
+
+  2. Clone [the problem-specifications repository](https://github.com/exercism/problem-specifications).
+
+  3. Run `configlet generate . --only name_of_new_exercise` from the root of this repository.
 
-4. Check if there is canonical data for the exercise you're adding.
+* Check if there is canonical data for the exercise you're adding.
 This can be found at `https://github.com/exercism/problem-specifications/tree/master/exercises/EXERCISE-SLUG/canonical-data.json`.
 If there is canonical data for your exercise then you should follow this when making the tests.
 We aim to follow the canonical data as closely as possible in our tests to ensure thorough test coverage.