That's a fair enough comment: any order was specified in the problem spec. I added to @tests: 

my @tests = (
    [[2,7,11,15], 9, [0,1]],
    [[2,7,11,15], 9, [1,0]],
    [[3,2,4], 6, [1,2]],
    [[3,2,4], 6, [2,1]],
    [[3,3], 6, [0,1]],
    [[3,3], 6, [1,0]],
);

[download]

Modified is_deeply: 

for my $test (@tests) {
    is_deeply
        sort_arrayref(two_sum($test->[INPUT], $test->[TARGET])),
        sort_arrayref($test->[EXPECTED]);
}

[download]

Appended a new subroutine: 

sub sort_arrayref {
    my ($aref) = @_;

    return [ sort { $a <=> $b } @$aref ];
}

[download]

Output now:

1..6
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6

[download]

— Ken

In reply to Re^2: LeetCode Problem #1 - Two Sum - Improve and/or discuss. by kcott
in thread LeetCode Problem #1 - Two Sum - Improve and/or discuss. by kcott

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.