Less confusing error messages? What i strange concept!

Truth be told, i love it but i never expected that i would ever see it happen.

Sadly though, my idea of a contains() function for arrays was refused by the core team, so array checking is still ugly and error-prone. Guess i have to be content with ONE major improvement per release. I mean, i have Array::Contains, but that only runs at a fraction of the speed of a native solution...

How does it compare speed-wise with List::Util::any? I've always found that fast enough for my needs but maybe I'm just not very demanding.

---

🦛

"How does it compare speed-wise ..."

A very quick benchmark shows no appreciable difference.

#!/usr/bin/env perl

use strict;
use warnings;

use Array::Contains;
use List::Util 'any';
use Benchmark 'cmpthese';

my @base = 'A' .. 'Z';
my @search = map +($_, lc), @base;

print "\@base[@base]\n";
print "\@search[@search]\n";

cmpthese 0 => {
    lua => \&lua,
    acc => \&acc,
};

sub lua {
    for my $x (@search) {
        my $bool = any { $_ eq $x } @base;
    }

    return;
}

sub acc {
    for my $x (@search) {
        my $bool = contains($x, \@base);
    }

    return;
}
[download]

The check on the arrays was the same on each run:

@base[A B C ... X Y Z]
@search[A a B b C c ... X x Y y Z z]
[download]

Here's the results of three runs:

       Rate lua acc
lua 15544/s  -- -1%
acc 15622/s  1%  --

       Rate acc lua
acc 15777/s  -- -1%
lua 15905/s  1%  --

       Rate acc lua
acc 15782/s  -- -0%
lua 15857/s  0%  --
[download]

— Ken