But why live with the warnings and the uncertainty about the function's future?
perl -wE '
my @foo = (1, 2, 3);
my @bar = (1, 2, 3);
my @baz = (1, 2, 4);
say "@foo" eq "@bar";
say "@foo" eq "@baz";
'
1
Or:
perl -MTest::Deep::NoTest=eq_deeply -wE '
my @foo = (1, 2, 3);
my @bar = (1, 2, 3);
my @baz = (1, 2, 4);
say eq_deeply \@foo, \@bar;
say eq_deeply \@foo, \@baz;
'
1
0
smartmatch:
perl -wE '
my @foo = (1, 2, 3);
my @bar = (1, 2, 3);
my @baz = (1, 2, 4);
say @foo ~~ @bar;
say @foo ~~ @baz;
'
Smartmatch is experimental at -e line 5.
Smartmatch is experimental at -e line 6.
1
The way forward always starts with a minimal test.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
