Re: How does List.map: { .say } work?

2009-11-04 Thread TSa (Thomas Sandlaß)
HaloO, On Tuesday, 3. November 2009 17:13:22 Carl Mäsak wrote: > That would make statement modifier for loops less useful. For those, > there's nowhere to put the lambda arrow. > > ++$_ for @things; I think this is resolved with the is ref binding which implies that the thingy that is bound to

Re: How does List.map: { .say } work?

2009-11-03 Thread Carl Mäsak
Moritz (>), Solomon (>>), Moritz (>>>): >> > the current spec doesn't allow immutable containers to call .map with a >> > block that implicitly uses $_ as an implicit parameter. >> > >> > Here's why: >> > >> > S06 says >> > >> >> The C<$_> variable functions as a placeholder in a block without any

Re: How does List.map: { .say } work?

2009-11-03 Thread Moritz Lenz
On Mon, Nov 02, 2009 at 10:16:39AM -0500, Solomon Foster wrote: > On Mon, Nov 2, 2009 at 9:53 AM, Moritz Lenz wrote: > > Hi, > > > > the current spec doesn't allow immutable containers to call .map with a > > block that implicitly uses $_ as an implicit parameter. > > > > Here's why: > > > > S06 s

Re: How does List.map: { .say } work?

2009-11-02 Thread Raphael Descamps
Am Montag, den 02.11.2009, 14:33 -0500 schrieb Solomon Foster: > On Mon, Nov 2, 2009 at 2:03 PM, Solomon Foster wrote: > > On Mon, Nov 2, 2009 at 10:21 AM, Carl Mäsak wrote: > >> Solomon (>), Moritz (>>): > the current spec doesn't allow immutable containers to call .map with a > block

Re: How does List.map: { .say } work?

2009-11-02 Thread Solomon Foster
On Mon, Nov 2, 2009 at 2:03 PM, Solomon Foster wrote: > On Mon, Nov 2, 2009 at 10:21 AM, Carl Mäsak wrote: >> Solomon (>), Moritz (>>): the current spec doesn't allow immutable containers to call .map with a block that implicitly uses $_ as an implicit parameter. Here's why: >

Re: How does List.map: { .say } work?

2009-11-02 Thread Solomon Foster
On Mon, Nov 2, 2009 at 10:21 AM, Carl Mäsak wrote: > Solomon (>), Moritz (>>): >>> the current spec doesn't allow immutable containers to call .map with a >>> block that implicitly uses $_ as an implicit parameter. >>> >>> Here's why: >>> >>> S06 says >>> The C<$_> variable functions as a pla

Re: How does List.map: { .say } work?

2009-11-02 Thread Carl Mäsak
Solomon (>), Moritz (>>): >> the current spec doesn't allow immutable containers to call .map with a >> block that implicitly uses $_ as an implicit parameter. >> >> Here's why: >> >> S06 says >> >>> The C<$_> variable functions as a placeholder in a block without any >>> other placeholders or sign

Re: How does List.map: { .say } work?

2009-11-02 Thread Solomon Foster
On Mon, Nov 2, 2009 at 9:53 AM, Moritz Lenz wrote: > Hi, > > the current spec doesn't allow immutable containers to call .map with a > block that implicitly uses $_ as an implicit parameter. > > Here's why: > > S06 says > >> The C<$_> variable functions as a placeholder in a block without any >> o

How does List.map: { .say } work?

2009-11-02 Thread Moritz Lenz
Hi, the current spec doesn't allow immutable containers to call .map with a block that implicitly uses $_ as an implicit parameter. Here's why: S06 says > The C<$_> variable functions as a placeholder in a block without any > other placeholders or signature. Any bare block without placeholders