Author: lwall Date: 2009-09-11 20:28:54 +0200 (Fri, 11 Sep 2009) New Revision: 28219
Modified: docs/Perl6/Spec/S06-routines.pod Log: [S06] supply missing list splitting primitive as a form of binding, masak++ for cf http://research.sun.com/projects/plrg/Publications/ICFPAugust2009Steele.pdf Modified: docs/Perl6/Spec/S06-routines.pod =================================================================== --- docs/Perl6/Spec/S06-routines.pod 2009-09-11 17:35:46 UTC (rev 28218) +++ docs/Perl6/Spec/S06-routines.pod 2009-09-11 18:28:54 UTC (rev 28219) @@ -15,8 +15,8 @@ Created: 21 Mar 2003 - Last Modified: 7 Sep 2009 - Version: 114 + Last Modified: 11 Sep 2009 + Version: 115 This document summarizes Apocalypse 6, which covers subroutines and the @@ -833,11 +833,20 @@ Slurpy scalars still impose list context on their arguments. -Slurpy parameters are treated lazily -- the list is only flattened +Single slurpy parameters are treated lazily -- the list is only flattened into an array when individual elements are actually accessed: @fromtwo = tail(1..Inf); # @fromtwo contains a lazy [2..Inf] +[Conjecture: However, if you use two or more slurpy arrays in a +signature, the list is instead evaluated in hyper context, and will +be asked to split itself into the number of lists corresponding to +the number of slurpies so declared. A non-hyperable list will return +failure for this splitting operation, so the signature should only bind +on parallelizable list operations. Likewise a list that "too short to +split" fails to bind, so a separate signature may match empty lists, +and perhaps singletons, if we define "too short" that way).] + You can't bind to the name of a slurpy parameter: the name is just there so you can refer to it within the body.
