Menengah Exercism • csharp

Proverb

Ringkasan Tantangan

For want of a horseshoe nail, a kingdom was lost, or so the saying goes. Output the full text of this proverbial rhyme.

Visit the proverb exercise on Exercism to read the full instructions and download the exercise files.

Dig Deeper

Use LINQ

LINQ

using System;
using System.Linq;

public static class Proverb
{
    public static string[] Recite(string[] subjects)
    {
        if (subjects.Length == 0)
            return Array.Empty<string>();

        return subjects.Zip(subjects.Skip(1))
            .Select((pair => $"For want of a {pair.First} the {pair.Second} was lost."))
            .Append($"And all for the want of a {subjects.First()}.")
            .ToArray();
    }
}

In this approach, we’ll use LINQ to iterate over the subjects and compose the song’s lines.

Song structure

Before we start writing code, let’s examine the structure of the song’s lines we’ll need to return. There are three different situations we have to handle:

No subjects: return an empty array
One subject: return an array with one element: “And all for the want of a <SUBJECT>.”
Multiple subjects: return an array of length equal to the number of subjects. All but the last line are of the form: “For want of a <SUBJECT> the <NEXT_SUBJECT> was lost.”, where “<SUBJECT>” and “<NEXT_SUBJECT>” are adjacent subjects (subjects at index 0 and 1, then 1 and 2, etc.). The last line is of the form “And all for the want of a <FIRST_SUBJECT>.”, where “<FIRST_SUBJECT>” is the first subject.

Subjects: none

Let’s check the number of subjects via the array’s Length property. If the length is equal to 0, return an empty array:

if (subjects.Length == 0)
    return Array.Empty<string>();

Alternatively, you could also use the Any() method:

if (!subjects.Any())
    return Array.Empty<string>();

As the `!` operator can be easy to miss whilst reading code, try to write code that doesn't use negation (where possible).

Subjects: one

The case for one subject is easy enough:

if (subjects.Length == 1)
    return $"And all for the want of a {subjects[0]}."

Or alternatively using First():

if (subjects.Length == 1)
    return $"And all for the want of a {subjects.First()}."

This has the benefit of being more expressive and would also work for collection that don’t implement the ICollection<T> interface (e.g. IEnumerable<T>).

Subjects: multiple

Handling multiple subjects is where the fun begins! To reiterate, there will be one line in the returned array for each adjacent subject pair.

Breaking up of a collection into adjacent sub-collection of a certain size of sometimes also referred to as a _sliding window_.

Let’s look at an example, where the subjects array contains "nail", "shoe" and "horse". There are two adjacent subject pairs in this array:

"nail" and "shoe"
"shoe" and "horse"

These pairs then should result in the following two lines:

"For want of a nail the shoe was lost."
"For want of a shoe the horse was lost."

So how do we use LINQ to create an enumerable of these pairs? We can use a little trick by calling the Zip() method on the subjects array with its arguments being the same subjects array but without the first element.

What Zip() does is that it works on two enumerables and creates a new enumerable where element is a pair (tuple) of values, the first element being the n-th value of the first enumerable and the second element being the n-th value of the second enumerable.

The number of elements returned by `Zip()` is equal to the minimum of the lengths of both enumerables.

As an example:

new[] { "nail", "shoe", "horse" }.Zip({ "shoe", "horse" })

will return an enumerable that contains two elements (tuples):

{ ("nail", "shoe"), ("shoe", "horse") }

We can then use the Select() method to convert these pairs (tuples) into the correct string:

subjects
  .Zip(subjects.Skip(1))
  .Select((pair => $"For want of a {pair.First} the {pair.Second} was lost."))

And all for the want of a …

The last line is of the form: “And all for the want of a <FIRST_SUBJECT>.”, which translates to:

$"And all for the want of a {subjects.First()}."

We can then add this line to the end of the other lines by calling [Append()][enumerable.append]:

.Append($"And all for the want of a {subjects.First()}.")

Putting it all together

The final step is to call ToArray() to return the correct collection type, giving us the following implementation:

if (subjects.Length == 0)
    return Array.Empty<string>();

if (subjects.Length == 1)
    return $"And all for the want of a {subjects.First()}."

return subjects.Zip(subjects.Skip(1))
    .Select((subject => $"For want of a {subject.First} the {subject.Second} was lost."))
    .Append($"And all for the want of a {subjects.First()}.")
    .ToArray();

Simplification

As this code also works for subjects with one element, we can remove the custom logic for handling one element:

if (subjects.Length == 0)
    return Array.Empty<string>();

return subjects.Zip(subjects.Skip(1))
    .Select((pair => $"For want of a {pair.First} the {pair.Second} was lost."))
    .Append($"And all for the want of a {subjects.First()}.")
    .ToArray();

Alternative: single expression

Can we do anything about to move the logic of that if statement to within our main method chain? Well, yes we can! To so, we’ll remove the if statement and replace the call to Append() with a call to [Concat() method]. Using the ternary operator, we’ll pass either an empty array (if there are no subjects) or an array with just one element (“And all for the want of a…”) as its argument:

.Concat(subjects.Any() ? new[] { $"And all for the want of a {subjects.First()}." } : Array.Empty<string>())

The reason we need to use the ternary operator is because subjects.First() would throw an exception if there are no subjects.

Shortening

As our method now contains only a single expression, we could rewrite it to an expression-bodied method:

public static string[] Recite(string[] subjects) =>
    subjects.Zip(subjects.Skip(1))
        .Select((subject => $"For want of a {subject.First} the {subject.Second} was lost."))
        .Concat(subjects.Any() ? new[] { $"And all for the want of a {subjects.First()}." } : Array.Empty<string>())
        .ToArray();

Use a for loop

`for` loop

public static class Proverb
{
    public static string[] Recite(string[] subjects)
    {
        if (subjects.Length == 0)
            return Array.Empty<string>();

        var lines = new string[subjects.Length];

        for (int i = 0; i < subjects.Length - 1; i++)
            lines[i] = $"For want of a {subjects[i]} the {subjects[i + 1]} was lost.";

        lines[^1] = $"And all for the want of a {subjects[0]}.";

        return lines;
    }
}

This approach uses a for loop to iterate over the subjects and compose the song’s lines.

Song structure

Before we start writing code, let’s examine the structure of the song’s lines we’ll need to return. There are three different situations we have to handle:

No subjects: return an empty array
One subject: return an array with one element: “And all for the want of a <SUBJECT>.”
Multiple subjects: return an array of length equal to the number of subjects. All but the last line are of the form: “For want of a <SUBJECT> the <NEXT_SUBJECT> was lost.”, where “<SUBJECT>” and “<NEXT_SUBJECT>” are adjacent subjects (subjects at index 0 and 1, then 1 and 2, etc.). The last line is of the form “And all for the want of a <FIRST_SUBJECT>.”, where “<FIRST_SUBJECT>” is the first subject.

Subjects: none

Let’s check the number of subjects via the array’s Length property. If the length is equal to 0, return an empty array:

if (subjects.Length == 0)
    return Array.Empty<string>();

Subjects: one

To implement the case for one subject, we can just return an array with one element that has the correct structure:

return new[] { $"And all for the want of a {subjects[0]}." };

Subjects: multiple

Handling multiple subjects is where the fun begins!

As the array we want to return must have a length equal to the number of subjects, let’s start by defining this array:

var lines = new string[subjects.Length];

To reiterate, there will be one line in the returned array for each adjacent subject pair.

Breaking up of a collection into adjacent sub-collection of a certain size of sometimes also referred to as a _sliding window_.

Let’s look at an example, where the subjects array contains "nail", "shoe" and "horse". There are two adjacent subject pairs in this array:

"nail" and "shoe"
"shoe" and "horse"

These pairs then should result in the following two lines:

"For want of a nail the shoe was lost."
"For want of a shoe the horse was lost."

So how do we process there adjacent subject pairs? If we think of the pairs as pairs of indexes (0 and 1, 1 and 2), we can see that the starting index of these pairs (0 and 1) is less than the length of the subjects minus one. That translates to:

for (int i = 0; i < subjects.Length - 1; i++)

Within the for loop, we set each line using its correct value, using the subject at index i and its adjacent subject at index i + 1:

for (int i = 0; i < subjects.Length - 1; i++)
    lines[i] = $"For want of a {subjects[i]} the {subjects[i + 1]} was lost.";

And all for the want of a …

The last line is of the form: “And all for the want of a <FIRST_SUBJECT>.”, which translates to:

lines[lines.Length - 1] = $"And all for the want of a {subjects[0]}."

The last line’s index is calculated via lines.Length - 1, but this is quite ugly, so is there a more elegant way? Why yes, there is, by using the index from end operator (^):

lines[^1] = $"And all for the want of a {subjects[0]}."

Simplification

As this code also works for subjects with one element, we can remove the code we’ve previously written to handle one subject.

Putting it all together

The final step is to return the lines, giving us:

if (subjects.Length == 0)
    return Array.Empty<string>();

var lines = new string[subjects.Length];

for (int i = 0; i < subjects.Length - 1; i++)
    lines[i] = $"For want of a {subjects[i]} the {subjects[i + 1]} was lost.";

lines[^1] = $"And all for the want of a {subjects[0]}.";

return lines;

Source: Exercism csharp/proverb