use warnings;
use strict;

use Data::Dumper;

my @arr = qw( a b c );
my %h;
@h{@arr} = (3, 4, 5);  # @hash{keys} = values
print Dumper(\%h);

__END__
Output:
$VAR1 = {
          'c' => 5,
          'b' => 4,
          'a' => 3
        };
[download]

Thanks choroba and all the other monks who replied...

The way forward always starts with a minimal test.

Hash slices are useful, but assigning a scalar to them is less useful. Perl could warn in that case, but I don't know that it should.

@hash{@array} = 'foo'; # converted to a 1-element list
@hash{@array} = ('foo'); # equivalent
@hash{@array} = ('foo', undef, undef); # equivalent
@hash{@array} = ('foo', 'foo', 'foo'); # arguably should be equivalent
[download]

Why doesn't Perl have a warning for the [@hash{@array} = 'foo'] case?

I would say because an empty hash slice assignment | index list is a perfectly valid thing. It's equivalent to
    $hash{$_} = 'foo' for @array;
which also does not (and should not) warn.

c:\@Work\Perl\monks>perl -wMstrict -MData::Dump -le
"my %hash = qw(a 1  b 2);
 my @array;
 @hash{@array} = 'foo';
 dd \%hash;
 ;;
 $hash{$_} = 'foo' for @array;
 dd \%hash;
"
{ a => 1, b => 2 }

{ a => 1, b => 2 }
[download]

Because you're effectively using a hash slice.

What that does is the @ in front of the hash presents its keys. Then if any of the keys match any elements in the array, those values are returned:

my %h = (1 => 'a', 2 => 'b', 3 => 'c');
my @a = (2, 3);

my @b = @h{@a};

print "$_\n" for @b;

__END__
b
c
[download]

-stevieb

Replying to myself for the archives ...

Not more than a couple of days after posting this and learning from the replies, I had cause to use a hash slice in my work. In a sub that can be called with a single argument consisting of a single value or a list, I was returning a hashref of objects in all cases.

Much better to return the object directly if the sub is called with a single value:

return (scalar keys %data == 1) ? @data{ keys %data } : \%data;
[download]

Very cool. Thanks again, monks.