From @AlexDaniel

Code​:
([+] **)(4, 8, 15).say

Result​:
Cannot resolve caller Numeric(HyperWhatever​: ); none of these signatures match​:
  (Mu​:U \v​: *%_)
  in block <unit> at -e line 1

I guess it is supposed to work?

From @coke

On Thu, 19 Jan 2017 18​:10​:27 -0800, alex.jakimenko@​gmail.com wrote​:

I guess it is supposed to work?

Why?

--
Will "Coke" Coleda

The RT System itself - Status changed from 'new' to 'open'

From @AlexDaniel

Gut feeling.

On 2017-01-20 08​:17​:06, coke wrote​:

On Thu, 19 Jan 2017 18​:10​:27 -0800, alex.jakimenko@​gmail.com wrote​:

I guess it is supposed to work?

Why?

From @zoffixznet

On Thu, 19 Jan 2017 18​:10​:27 -0800, alex.jakimenko@​gmail.com wrote​:

I guess it is supposed to work?

Isn't this the case where HyperWhatever is used as a term by itself, so you're passing it itself to [+] metaop and doesn't curry and hence its complaining.

Same's with regular Whatever​:

<Zoffix> m​: dd ([+] *)(42)
<camelia> rakudo-moar f97d5c​: OUTPUT«Cannot resolve caller Numeric(Whatever​: ); none of these signatures match​:␤ (Mu​:U \v​: *%_)␤ in block <unit> at <tmp> line 1␤

Also, I believe HyperWhatever doesn't just slurp the args and sub them in its place, but rather performs the operation for each of them. It basically curries into `sub (*@​_) { map &c, @​_ }`, where &c is he "curry"​:
<Zoffix> m​: dd (**.&[+](1))(4, 8, 15
<camelia> rakudo-moar f97d5c​: OUTPUT«(5, 9, 16).Seq␤»

So even if it curried in the OP example, it'd just return the same seq back, since the [+] would be called with 1 arg each time.

From @AlexDaniel

This makes sense.

On 2017-01-20 09​:54​:37, cpan@​zoffix.com wrote​:

On Thu, 19 Jan 2017 18​:10​:27 -0800, alex.jakimenko@​gmail.com wrote​:

I guess it is supposed to work?

Isn't this the case where HyperWhatever is used as a term by itself,
so you're passing it itself to [+] metaop and doesn't curry and hence
its complaining.

Same's with regular Whatever​:

<Zoffix> m​: dd ([+] *)(42)
<camelia> rakudo-moar f97d5c​: OUTPUT«Cannot resolve caller
Numeric(Whatever​: ); none of these signatures match​:␤ (Mu​:U \v​:
*%_)␤ in block <unit> at <tmp> line 1␤

Also, I believe HyperWhatever doesn't just slurp the args and sub them
in its place, but rather performs the operation for each of them. It
basically curries into `sub (*@​_) { map &c, @​_ }`, where &c is he
"curry"​:
<Zoffix> m​: dd (**.&[+](1))(4, 8, 15
<camelia> rakudo-moar f97d5c​: OUTPUT«(5, 9, 16).Seq␤»

So even if it curried in the OP example, it'd just return the same seq
back, since the [+] would be called with 1 arg each time.

From @moritz

Whatever and HyperWhatever doesn't behave magically inside of an argument list, so I see no bug here.

@moritz - Status changed from 'open' to 'rejected'