trackler 2.2.1.177 → 2.2.1.178

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2e5bcb62b38646413cb1b774d068463bb8f4a70c
-  data.tar.gz: 955ab5796404df47072cdb28d09600e3edbff1bd
+  metadata.gz: ca50d7d1d4b2ee947e08370ff3fc95b678fc13d5
+  data.tar.gz: 1ab07f551bddfcefc505f1b1b0f03c3e0694d618
 SHA512:
-  metadata.gz: fd13a222bd29b3d53520d44f84b0cee0fad4dedf5b27de00143c1738689a5de48b74c1f17ceb92bcbb2f260d494b9b1f973b6d03574659c2cbac50a9e0a61f89
-  data.tar.gz: 1f33b0a29f2a0800d0ef2151dd0f9a82b0659e504a2557d594b6d168f7d9587a4dd64d43764dea2f4bb2b13adfd6dc858088e116008f14377e404627e64c1a8f
+  metadata.gz: f04d0fce48e09d09e4666d18fcf1babc9968c33d242ee088c706400fd892b28728875ce4f9d0730540b72c4effa90b97a9e31f130ff39bc3fbf0839ad97eecf5
+  data.tar.gz: 7fc76eaac7b30187cde6435ac97632de98a38eec8c51913d93216c05771fac00c14c1af2fb87e6e33916266dc3d38cbdb33151e009ef0e0f59f21200d0acc47e

data/lib/trackler/version.rb

@@ -1,3 +1,3 @@
 module Trackler
-  VERSION = "2.2.1.177"
+  VERSION = "2.2.1.178"
 end

data/tracks/go/config/exercise_readme.go.tmpl

@@ -8,10 +8,10 @@
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/docs/TESTS.md

@@ -7,7 +7,7 @@ $ go test
 
 ### Running benchmarks
 
-Most exercises contain benchmarks, that you can use to determine how changes to your solution affect its performance. To run the benchmarks for an exercise use the command `go test -bench .` inside the exercise directory.
+Most exercises contain benchmarks, that you can use to determine how changes to your solution affect its performance. To run the benchmarks for an exercise use the command `go test -v --bench . --benchmem` inside the exercise directory.
 
 ### Testable examples
 

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

@@ -29,10 +29,10 @@ Solve this one yourself using other basic tools instead.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -11,10 +11,10 @@ like Portable Network Graphics to its acronym (PNG).
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/all-your-base/README.md

@@ -50,10 +50,10 @@ returns one of following messages:
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -33,10 +33,10 @@ score is 257, your program should only report the eggs (1) allergy.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -75,10 +75,10 @@ Replacing these with valid numbers gives:
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -10,10 +10,10 @@ Given `"listen"` and a list of candidates like `"enlists" "google"
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/armstrong-numbers/README.md

@@ -5,7 +5,7 @@ An [Armstrong number](https://en.wikipedia.org/wiki/Narcissistic_number) is a nu
 For example:
 
 - 9 is an Armstrong number, because `9 = 9^1 = 9`
-- 10 is *not* an Armstrong number, because `10 != 1^2 + 0^2 = 2`
+- 10 is *not* an Armstrong number, because `10 != 1^2 + 0^2 = 1`
 - 153 is an Armstrong number, because: `153 = 1^3 + 5^3 + 3^3 = 1 + 125 + 27 = 153`
 - 154 is *not* an Armstrong number, because: `154 != 1^3 + 5^3 + 4^3 = 1 + 125 + 64 = 190`
 
@@ -15,10 +15,10 @@ Write some code to determine whether a number is an Armstrong number.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/atbash-cipher/README.md

@@ -32,10 +32,10 @@ things based on word boundaries.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/bank-account/README.md

@@ -30,10 +30,10 @@ Have fun!
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/beer-song/README.md

@@ -324,10 +324,10 @@ experiment make the code better? Worse? Did you learn anything from it?
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/binary-search-tree/README.md

@@ -57,10 +57,10 @@ And if we then added 1, 5, and 7, it would look like this
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/binary-search/README.md

@@ -38,10 +38,10 @@ A binary search is a dichotomic divide and conquer search algorithm.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -34,10 +34,10 @@ So: `101 => 1*2^2 + 0*2^1 + 1*2^0 => 1*4 + 0*2 + 1*1 => 4 + 1 => 5 base 10`.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -17,10 +17,10 @@ He answers 'Whatever.' to anything else.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/book-store/README.md

@@ -87,10 +87,10 @@ Only integer calculations are necessary for this exercise.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -64,10 +64,10 @@ support two operations:
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/bracket-push/README.md

@@ -8,10 +8,10 @@ and nested correctly.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -20,10 +20,10 @@ that the sum of the coins' value would equal the correct amount of change.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/circular-buffer/README.md

@@ -54,10 +54,10 @@ the buffer is once again full.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -10,10 +10,10 @@ Two clocks that represent the same time should be equal to each other.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/collatz-conjecture/README.md

@@ -30,10 +30,10 @@ Resulting in 9 steps. So for input n = 12, the return value would be 9.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -34,10 +34,10 @@ won since `O` didn't connect top and bottom.
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

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

@@ -24,10 +24,10 @@ of times, passing in strings, and afterwards call the "lines",
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.

data/tracks/go/exercises/crypto-square/README.md

@@ -12,11 +12,15 @@ regarded as forming a rectangle when printed with intervening newlines.
 
 For example, the sentence
 
-> If man was meant to stay on the ground, god would have given us roots.
+```text
+"If man was meant to stay on the ground, god would have given us roots."
+```
 
 is normalized to:
 
-> ifmanwasmeanttostayonthegroundgodwouldhavegivenusroots
+```text
+"ifmanwasmeanttostayonthegroundgodwouldhavegivenusroots"
+```
 
 The plaintext should be organized in to a rectangle.  The size of the
 rectangle (`r x c`) should be decided by the length of the message,
@@ -27,13 +31,13 @@ Our normalized text is 54 characters long, dictating a rectangle with
 `c = 8` and `r = 7`:
 
 ```text
-ifmanwas
-meanttos
-tayonthe
-groundgo
-dwouldha
-vegivenu
-sroots
+"ifmanwas"
+"meanttos"
+"tayonthe"
+"groundgo"
+"dwouldha"
+"vegivenu"
+"sroots  "
 ```
 
 The coded message is obtained by reading down the columns going left to
@@ -42,41 +46,40 @@ right.
 The message above is coded as:
 
 ```text
-imtgdvsfearwermayoogoanouuiontnnlvtwttddesaohghnsseoau
+"imtgdvsfearwermayoogoanouuiontnnlvtwttddesaohghnsseoau"
 ```
 
-Output the encoded text in chunks.  Phrases that fill perfect rectangles
-`(r X c)` should be output `c` chunks of `r` length, separated by spaces.
-Phrases that do not fill perfect rectangles will have `n` empty spaces.
-Those spaces should be distributed evenly, added to the end of the last
-`n` chunks.
+Output the encoded text in chunks that fill perfect rectangles `(r X c)`,
+with `c` chunks of `r` length, separated by spaces. For phrases that are
+`n` characters short of the perfect rectangle, pad each of the last `n`
+chunks with a single trailing space.
 
 ```text
-imtgdvs fearwer mayoogo anouuio ntnnlvt wttddes aohghn  sseoau 
+"imtgdvs fearwer mayoogo anouuio ntnnlvt wttddes aohghn  sseoau "
 ```
 
 Notice that were we to stack these, we could visually decode the
 cyphertext back in to the original message:
 
 ```text
-imtgdvs
-fearwer
-mayoogo
-anouuio
-ntnnlvt
-wttddes
-aohghn
-sseoau
+"imtgdvs"
+"fearwer"
+"mayoogo"
+"anouuio"
+"ntnnlvt"
+"wttddes"
+"aohghn "
+"sseoau "
 ```
 
 ## Running the tests
 
 To run the tests run the command `go test` from within the exercise directory.
 
-If the test suite contains benchmarks, you can run these with the `-bench`
-flag:
+If the test suite contains benchmarks, you can run these with the `--bench` and `--benchmem`
+flags:
 
-    go test -bench .
+    go test -v --bench . --benchmem
 
 Keep in mind that each reviewer will run benchmarks on a different machine, with
 different specs, so the results from these benchmark tests may vary.