Avatar of 4d47

4d47's solution

to Two Fer in the Perl 6 Track

Test suite

Two-fer or 2-fer is short for two for one. One for you and one for me.

"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."


Remember to check out the Perl 6 documentation and 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'.



Submitting Incomplete Solutions

It's possible to submit an incomplete solution so you can see how others have completed the exercise.


#!/usr/bin/env perl6
use v6;
use Test;
use JSON::Fast;
use lib $?FILE.IO.dirname; #`[Look for the module inside the same directory as this test file.]
use TwoFer;
plan 3; #`[This is how many tests we expect to run.]

my Version:D $version = v2; #`[The version we will be matching against the exercise.]

#`[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 TwoFer.^ver !~~ $version {
  warn "\nExercise version mismatch. Further tests may fail!"
    ~ "\nTwoFer is {TwoFer.^ver.gist}. "
    ~ "Test is {$version.gist}.\n";

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><name> ??
    two-fer(.<input><name>) !!
    |.<expected description>;

=head2 Canonical Data
=begin code
  "exercise": "two-fer",
  "version": "1.2.0",
  "cases": [
      "description": "no name given",
      "property": "twoFer",
      "input": {
        "name": null
      "expected": "One for you, one for me."
      "description": "a name given",
      "property": "twoFer",
      "input": {
        "name": "Alice"
      "expected": "One for Alice, one for me."
      "description": "another name given",
      "property": "twoFer",
      "input": {
        "name": "Bob"
      "expected": "One for Bob, one for me."
=end code
unit module TwoFer:ver<1>;

sub two-fer (Str $name = 'you' --> Str) is export {
  "One for $name, one for me."

What can you learn from this solution?

A huge amount can be learnt from reading other people’s code. This is why we wanted to give exercism users the option of making their solutions public.

Here are some questions to help you reflect on this solution and learn the most from it.

  • What compromises have been made?
  • Are there new concepts here that I could read more about to develop my understanding?