It shouldn't do, unless your smart match operands also happen to be objects that override bitwise-or. (For example, Math::BigInt does.)
The match($a, $b) function really is saner though. And faster for that matter. (Though the real smartmatch operator beats each hands down!)
use v5.18;
use match::simple -all;
use Benchmark qw( cmpthese );
$::A = 3;
$::B = [1 .. 5];
cmpthese(-1, {
'match' => q[ match($::A, $::B) ],
'M' => q[ $::A |M| $::B ],
'~~' => q[ no warnings 'experimental::smartmatch'; $::A ~~ $::B
+ ],
});
__END__
Rate M match ~~
M 11487/s -- -69% -99%
match 36540/s 218% -- -97%
~~ 1420284/s 12265% 3787% --
Anybody willing to provide a patch for an XS implementation of match::simple::match() would be likely to have it accepted. ;-)
use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name
-
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.
|