LastOrDefault on Min/MaxBy returns first

[atifaziz]

Chaining MoreLINQ's LastOrDefault with MinBy or MaxBy returns the first element instead of the last one.

Below is a sample to reproduce the bug:

// Assuming:
// using MoreLinq;

var strings = new[]
{
    "foo", "bar", "baz", "qux", "quux", "quuz", "corge",
    "grault", "garply", "waldo", "fred", "plugh", "xyzzy", "thud"
};

Console.WriteLine("=== MinBy ===");
Console.WriteLine(strings.MinBy(s => s.Length).Last());
Console.WriteLine(strings.MinBy(s => s.Length).LastOrDefault());
Console.WriteLine("=== MaxBy ===");
Console.WriteLine(strings.MaxBy(s => s.Length).Last());
Console.WriteLine(strings.MaxBy(s => s.Length).LastOrDefault());

Expected:

=== MinBy ===
qux
qux
=== MaxBy ===
garply
garply

Instead, actual result when using version 3.3.2 (latest at time of reporting):

=== MinBy ===
qux
foo
=== MaxBy ===
garply
grault