[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl6-language
Subject:    [perl6/specs] 74b208: don't include positional names in API
From:       noreply () github ! com
Date:       2011-05-23 16:02:49
Message-ID: 20110523160249.9C92F42444 () smtp1 ! rs ! github ! com
[Download RAW message or body]

Branch: refs/heads/master
Home:   https://github.com/perl6/specs

Commit: 74b208c3d7dc6bc3fb913be3376492e2d72733f6
    https://github.com/perl6/specs/commit/74b208c3d7dc6bc3fb913be3376492e2d72733f6
Author: Larry Wall <larry@wall.org>
Date:   2011-05-23 (Mon, 23 May 2011)

Changed paths:
  M S06-routines.pod

Log Message:
-----------
don't include positional names in API

As suggested by masak++ and jnthn++, remove the names of positionals
from the public API.

In its place, substitute the more useful ability to treat positionals
as if they were named by the use of *numeric* keys.  That is, move the
ability to name positionals out of the binder and into the coercion
from hash to capture.  This answers the three objections to named positionals:
    * The positions of the positionals are already part of the public API.
    * This has no run-time overhead (unless you force this coercion to happen
	at run time, using prefix:<|> for instance).
    * People will use this because many external formats do not support captures.


[prev in list] [next in list] [prev in thread] [next in thread]