trackler 2.2.1.56 → 2.2.1.57

data/tracks/perl6/exercises/pangram/Example.pm6

@@ -0,0 +1,5 @@
+unit module Pangram:ver<1>;
+
+sub is-pangram (Str:D $string --> Bool:D) is export {
+  $string.lc.comb ⊇ ‘a’..‘z’
+}

data/tracks/perl6/exercises/pangram/Pangram.pm6

@@ -0,0 +1,4 @@
+unit module Pangram:ver<1>;
+
+sub is-pangram ($string) is export {
+}

data/tracks/perl6/exercises/pangram/README.md

@@ -0,0 +1,34 @@
+# Pangram
+
+Determine if a sentence is a pangram. A pangram (Greek: παν γράμμα, pan gramma,
+"every letter") is a sentence using every letter of the alphabet at least once.
+The best known English pangram is:
+> The quick brown fox jumps over the lazy dog.
+
+The alphabet used consists of ASCII letters `a` to `z`, inclusive, and is case
+insensitive. Input will not contain non-ASCII symbols.
+
+## Resources
+
+Remember to check out the Perl 6 [documentation](https://docs.perl6.org/) and
+[resources](https://perl6.org/resources/) pages for information, tips, and
+examples if you get stuck.
+
+## Running the tests
+
+There is a test suite and module included with the exercise.
+The test suite (a file with the extension `.t`) will attempt to run routines
+from the module (a file with the extension `.pm6`).
+Add/modify routines in the module so that the tests will pass! You can view the
+test data by executing the command `perl6 --doc *.t` (\* being the name of the
+test suite), and run the test suite for the exercise by executing the command
+`prove . --exec=perl6` in the exercise directory.
+You can also add the `-v` flag e.g. `prove . --exec=perl6 -v` to display all
+tests, including any optional tests marked as 'TODO'.
+
+## Source
+
+Wikipedia [https://en.wikipedia.org/wiki/Pangram](https://en.wikipedia.org/wiki/Pangram)
+
+## Submitting Incomplete Solutions
+It's possible to submit an incomplete solution so you can see how others have completed the exercise.

data/tracks/perl6/exercises/pangram/example.yaml

@@ -0,0 +1,17 @@
+exercise: Pangram
+version: 1
+plan: 12
+imports: '&is-pangram'
+tests: |
+  for $c-data<cases>.values -> %case-set {
+    is is-pangram(.<input>), |.<expected description> for %case-set<cases>.values;
+  }
+
+unit: module
+example: |
+  sub is-pangram (Str:D $string --> Bool:D) is export {
+    $string.lc.comb ⊇ ‘a’..‘z’
+  }
+stub: |
+  sub is-pangram ($string) is export {
+  }

data/tracks/perl6/exercises/pangram/pangram.t

@@ -0,0 +1,125 @@
+#!/usr/bin/env perl6
+use v6;
+use Test;
+use lib my $dir = $?FILE.IO.dirname;
+use JSON::Fast;
+
+my Str:D $exercise := 'Pangram';
+my Version:D $version = v1;
+my Str $module //= $exercise;
+plan 12;
+
+use-ok $module or bail-out;
+require ::($module);
+
+if ::($exercise).^ver !~~ $version {
+  warn "\nExercise version mismatch. Further tests may fail!"
+    ~ "\n$exercise is $(::($exercise).^ver.gist). "
+    ~ "Test is $($version.gist).\n";
+  bail-out 'Example version must match test version.' if %*ENV<EXERCISM>;
+}
+
+require ::($module) <&is-pangram>;
+
+my $c-data = from-json $=pod.pop.contents;
+for $c-data<cases>.values -> %case-set {
+  is is-pangram(.<input>), |.<expected description> for %case-set<cases>.values;
+}
+
+=head2 Canonical Data
+=begin code
+
+{
+  "exercise": "pangram",
+  "comments": [
+    "A pangram is a sentence using every letter of the alphabet at least once."
+  ],
+  "version": "1.3.0",
+  "cases": [
+    {
+      "description": "Check if the given string is an pangram",
+      "comments": [
+        "Output should be a boolean denoting if the string is a pangram or not."
+      ],
+      "cases": [
+        {
+          "description": "sentence empty",
+          "property": "isPangram",
+          "input": "",
+          "expected": false
+        },
+        {
+          "description": "recognizes a perfect lower case pangram",
+          "property": "isPangram",
+          "input": "abcdefghijklmnopqrstuvwxyz",
+          "expected": true
+        },
+        {
+          "description": "pangram with only lower case",
+          "property": "isPangram",
+          "input": "the quick brown fox jumps over the lazy dog",
+          "expected": true
+        },
+        {
+          "description": "missing character 'x'",
+          "property": "isPangram",
+          "input": "a quick movement of the enemy will jeopardize five gunboats",
+          "expected": false
+        },
+        {
+          "description": "another missing character, e.g. 'h'",
+          "property": "isPangram",
+          "input": "five boxing wizards jump quickly at it",
+          "expected": false
+        },
+        {
+          "description": "pangram with underscores",
+          "property": "isPangram",
+          "input": "the_quick_brown_fox_jumps_over_the_lazy_dog",
+          "expected": true
+        },
+        {
+          "description": "pangram with numbers",
+          "property": "isPangram",
+          "input": "the 1 quick brown fox jumps over the 2 lazy dogs",
+          "expected": true
+        },
+        {
+          "description": "missing letters replaced by numbers",
+          "property": "isPangram",
+          "input": "7h3 qu1ck brown fox jumps ov3r 7h3 lazy dog",
+          "expected": false
+        },
+        {
+          "description": "pangram with mixed case and punctuation",
+          "property": "isPangram",
+          "input": "\"Five quacking Zephyrs jolt my wax bed.\"",
+          "expected": true
+        },
+        {
+          "description": "upper and lower case versions of the same character should not be counted separately",
+          "property": "isPangram",
+          "input": "the quick brown fox jumps over with lazy FX",
+          "expected": false
+        }
+      ]
+    }
+  ]
+}
+
+=end code
+
+unless %*ENV<EXERCISM> {
+  skip-rest 'exercism tests';
+  exit;
+}
+
+subtest 'canonical-data' => {
+  (my $c-data-file = "$dir/../../problem-specifications/exercises/{
+    $dir.IO.resolve.basename
+  }/canonical-data.json".IO.resolve) ~~ :f ??
+    is-deeply $c-data, EVAL('from-json $c-data-file.slurp'), 'match problem-specifications' !!
+    flunk 'problem-specifications file not found';
+}
+
+INIT { $module = 'Example' if %*ENV<EXERCISM> }

data/tracks/perl6/exercises/phone-number/README.md

@@ -14,7 +14,7 @@ The format is usually represented as
 
 where `N` is any digit from 2 through 9 and `X` is any digit from 0 through 9.
 
-Your task is to clean up differently formated telephone numbers by removing punctuation and the country code (1) if present.
+Your task is to clean up differently formatted telephone numbers by removing punctuation and the country code (1) if present.
 
 For example, the inputs
 - `+1 (613)-995-0253`

data/tracks/perl6/exercises/two-fer/Example.pm6

@@ -0,0 +1,14 @@
+#`(
+  This is a 'stub' file. It's a little start on your solution.
+  It is not a complete solution though; you will have to write some code.
+
+  The ':ver<>' adverb defines the version of a module or class.
+  The version is checked in the test suite to ensure the exercise
+  and test suite line up. If the test is updated, it will indicate
+  to others who test your code that some tests may no longer pass.
+)
+unit module TwoFer:ver<1>;
+
+sub two-fer ($name = ‘you’) is export {
+  “One for $name, one for me.”
+}

data/tracks/perl6/exercises/two-fer/README.md

@@ -0,0 +1,38 @@
+# Two Fer
+
+`Two-fer` or `2-fer` is short for two for one. One for you and one for me.
+
+```text
+"One for X, one for me."
+```
+
+When X is a name or "you".
+
+If the given name is "Alice", the result should be "One for Alice, one for me."
+If no name is given, the result should be "One for you, one for me."
+
+
+## Resources
+
+Remember to check out the Perl 6 [documentation](https://docs.perl6.org/) and
+[resources](https://perl6.org/resources/) pages for information, tips, and
+examples if you get stuck.
+
+## Running the tests
+
+There is a test suite and module included with the exercise.
+The test suite (a file with the extension `.t`) will attempt to run routines
+from the module (a file with the extension `.pm6`).
+Add/modify routines in the module so that the tests will pass! You can view the
+test data by executing the command `perl6 --doc *.t` (\* being the name of the
+test suite), and run the test suite for the exercise by executing the command
+`prove . --exec=perl6` in the exercise directory.
+You can also add the `-v` flag e.g. `prove . --exec=perl6 -v` to display all
+tests, including any optional tests marked as 'TODO'.
+
+## Source
+
+This is an exercise to introduce users to basic programming constructs, just after hello World. [https://en.wikipedia.org/wiki/Two-fer](https://en.wikipedia.org/wiki/Two-fer)
+
+## Submitting Incomplete Solutions
+It's possible to submit an incomplete solution so you can see how others have completed the exercise.

data/tracks/perl6/exercises/two-fer/TwoFer.pm6

@@ -0,0 +1,15 @@
+#`(
+  This is a 'stub' file. It's a little start on your solution.
+  It is not a complete solution though; you will have to write some code.
+
+  The ':ver<>' adverb defines the version of a module or class.
+  The version is checked in the test suite to ensure the exercise
+  and test suite line up. If the test is updated, it will indicate
+  to others who test your code that some tests may no longer pass.
+)
+unit module TwoFer:ver<1>;
+
+sub two-fer ($name?) is export {
+  # Write your solution to pass the test suite here.
+  # Be sure to remove all stock comments once you are done!
+}

data/tracks/perl6/exercises/two-fer/example.yaml

@@ -0,0 +1,43 @@
+exercise: TwoFer
+version: 1
+plan: 5
+imports: '&two-fer'
+tests: |-
+  # Go through the cases and check that &two-fer gives us the correct response.
+  for $c-data<cases>.values {
+    is .<input> ??
+      two-fer(.<input>) !!
+      two-fer,
+      |.<expected description>;
+  }
+
+exercise_comment: The name of this exercise.
+module_comment: The name of the module file to be loaded.
+version_comment: The version we will be matching against the exercise.
+lib_comment: Look for the module inside the same directory as this test file.
+plan_comment: This is how many tests we expect to run.
+use_test_comment: Check that the module can be use-d.
+version_test_comment: "If the exercise is updated, we want to make sure other people testing\nyour code don't think you've made a mistake if things have changed!"
+imports_comment: Import '&two-fer' from 'TwoFer'
+exercism_comment: "Don't worry about the stuff below here for your exercise.\nThis is for Exercism folks to check that everything is in order."
+
+unit: module
+unit_comment: |-
+  #`(
+    This is a 'stub' file. It's a little start on your solution.
+    It is not a complete solution though; you will have to write some code.
+
+    The ':ver<>' adverb defines the version of a module or class.
+    The version is checked in the test suite to ensure the exercise
+    and test suite line up. If the test is updated, it will indicate
+    to others who test your code that some tests may no longer pass.
+  )
+example: |-
+  sub two-fer ($name = ‘you’) is export {
+    “One for $name, one for me.”
+  }
+stub: |-
+  sub two-fer ($name?) is export {
+    # Write your solution to pass the test suite here.
+    # Be sure to remove all stock comments once you are done!
+  }

data/tracks/perl6/exercises/two-fer/two-fer.t

@@ -0,0 +1,82 @@
+#!/usr/bin/env perl6
+use v6;
+use Test;
+use lib my $dir = $?FILE.IO.dirname; #`[Look for the module inside the same directory as this test file.]
+use JSON::Fast;
+
+my Str:D $exercise := 'TwoFer'; #`[The name of this exercise.]
+my Version:D $version = v1; #`[The version we will be matching against the exercise.]
+my Str $module //= $exercise; #`[The name of the module file to be loaded.]
+plan 5; #`[This is how many tests we expect to run.]
+
+#`[Check that the module can be use-d.]
+use-ok $module or bail-out;
+require ::($module);
+
+#`[If the exercise is updated, we want to make sure other people testing
+your code don't think you've made a mistake if things have changed!]
+if ::($exercise).^ver !~~ $version {
+  warn "\nExercise version mismatch. Further tests may fail!"
+    ~ "\n$exercise is $(::($exercise).^ver.gist). "
+    ~ "Test is $($version.gist).\n";
+  bail-out 'Example version must match test version.' if %*ENV<EXERCISM>;
+}
+
+#`[Import '&two-fer' from 'TwoFer']
+require ::($module) <&two-fer>;
+
+my $c-data = from-json $=pod.pop.contents;
+# Go through the cases and check that &two-fer gives us the correct response.
+for $c-data<cases>.values {
+  is .<input> ??
+    two-fer(.<input>) !!
+    two-fer,
+    |.<expected description>;
+}
+
+=head2 Canonical Data
+=begin code
+
+{
+  "exercise": "two-fer",
+  "version": "1.1.0",
+  "cases": [
+    {
+      "description": "no name given",
+      "property": "name",
+      "input": null,
+      "expected": "One for you, one for me."
+    },
+    {
+      "description": "a name given",
+      "property": "name",
+      "input": "Alice",
+      "expected": "One for Alice, one for me."
+    },
+    {
+      "description": "another name given",
+      "property": "name",
+      "input": "Bob",
+      "expected": "One for Bob, one for me."
+    }
+  ]
+}
+
+=end code
+
+#`[Don't worry about the stuff below here for your exercise.
+This is for Exercism folks to check that everything is in order.]
+unless %*ENV<EXERCISM> {
+  skip-rest 'exercism tests';
+  exit;
+}
+
+subtest 'canonical-data' => {
+  (my $c-data-file = "$dir/../../problem-specifications/exercises/{
+    $dir.IO.resolve.basename
+  }/canonical-data.json".IO.resolve) ~~ :f ??
+    is-deeply $c-data, EVAL('from-json $c-data-file.slurp'), 'match problem-specifications' !!
+    flunk 'problem-specifications file not found';
+}
+
+INIT { $module = 'Example' if %*ENV<EXERCISM> }

data/tracks/php/config.json

@@ -635,6 +635,19 @@
       "slug" : "all-your-base",
       "topics": [ ],
       "unlocked_by": "null"
+    },
+    {
+      "uuid": "9aa69058-1bce-4b65-bd26-7270698f97ea",
+      "slug": "rail-fence-cipher",
+      "core": false,
+      "unlocked_by": null,
+      "difficulty": 1,
+      "topics": [
+        "algorithms",
+        "cryptography",
+        "text_formatting",
+        "lists"
+      ]
     }
   ]
 }

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

@@ -0,0 +1,80 @@
+# 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.
+
+## Making the Test Suite Pass
+
+1. Get [PHPUnit].
+
+        % wget --no-check-certificate https://phar.phpunit.de/phpunit.phar
+        % chmod +x phpunit.phar
+
+2. Execute the tests for an assignment.
+
+        % phpunit.phar wordy/wordy_test.php
+
+[PHPUnit]: http://phpunit.de
+
+
+## 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.