The perldoc on keys clearly states

Called in list context, returns a list consisting of all the keys of the named hash…
but makes no attempt to explain why.

Googling around for an explanation also yielded no results.

Put very simply, why does 

        sub uniq {
            my %hash = map { $_ => 1 } @_;
            return keys %hash;
        }

[download]
work, but 
        sub uniq {
            return keys map { $_ => 1 } @_;
        }

[download]
not?

Edit:

I express my sincerest thanks to the monks for a warm welcome into the monastery.

Following the suggestions, I tried 

        sub uniq {
            # two pairs of braces around map
            return keys %{ { map { $_ => 1 } @_ } };
        }

[download]
which works perfectly fine.

However, prior to this, even before I posted the question, I experimented with 

        sub uniq {
            # single pair of braces around map
            return keys %{ map { $_ => 1 } @_ };
        }

[download]
and it did not work.

I had always believed that braces can convert a list with even number of elements into a valid HASHref, and modulo (%) can convert any valid HASHref into a hash.

The question now is this: if map just produces a list, why does it need two pairs of braces to emit a valid HASHref?

State. Science. Love.

In reply to Why does ‘keys’ need a named hash? by ankitpati

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.