From @smls

An item assignment inside a comma-separated list works as expected as long as the preceding element is a literal​:

  ➜ dd 1, my $x = 2, 3
  1
  $x = 2
  3

However when the preceding element is a sub or method call, the assignment for some reason gobbles the whole remaining list (as if it were a list assignment)​:

  ➜ dd Int(1), my $x = 2, 3
  1
  $x = $(2, 3)

  ➜ dd 1.Int, my $x = 2, 3
  1
  $x = $(2, 3)

I would assume this is a bug.

Unfortunately, http://design.perl6.org/S03.html#List_prefix_precedence does not go into details on how exactly the LHS of an assignment is supposed to determine item vs list precedence though.

From @jnthn

On Mon Jun 15 16​:22​:00 2015, smls75@​gmail.com wrote​:

An item assignment inside a comma-separated list works as expected as
long as the preceding element is a literal​:

➜ dd 1, my $x = 2, 3
1
$x = 2
3

However when the preceding element is a sub or method call, the
assignment for some reason gobbles the whole remaining list (as if it
were a list assignment)​:

➜ dd Int(1), my $x = 2, 3
1
$x = $(2, 3)

➜ dd 1.Int, my $x = 2, 3
1
$x = $(2, 3)

I would assume this is a bug.

Unfortunately, http://design.perl6.org/S03.html#List_prefix_precedence
does not go into details on how exactly the LHS of an assignment is
supposed to determine item vs list precedence though.

We didn't declare a fresh $*LEFTSIGIL per declarator, so we could end up with a postfix elsewhere "leaking" into the decision making. Fixed that now, and added a test in S03-operators/assignment.t.

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

@jnthn - Status changed from 'open' to 'resolved'