On Wednesday 25 October 2006 03:04, Trey Harris wrote:
> I'll let @Larry speak for @Larry, but at one point I was told that when
> C or C appear in signatures, those are roles, not classes; if
> you examined a particular Array or Hash, the class would be some
> implementation of the Array or Hash
In a message dated Sat, 28 Oct 2006, chromatic writes:
When you specify a type to constrain some operation, you specify that
the target entity must perform that role.
That statement is very concise and direct. If the fuzziness I observed
about the identity of the basic building block of type w
In a message dated Sat, 28 Oct 2006, Trey Harris writes:
In a message dated Sat, 28 Oct 2006, chromatic writes:
When you specify a type to constrain some operation, you specify that the
target entity must perform that role.
That statement is very concise and direct. If the fuzziness I observe
My initial inclination is to say that "where" clauses in a signature
are only there for pattern matching, and do not modify the official
type of the parameter within the function body. However, on a "subset"
the "where" clause is there precisely to contribute to the typing,
so if you want the extr
On Thu, Oct 26, 2006 at 03:17:27PM +0200, TSa wrote:
: HaloO,
:
: I wrote:
: >2) We have A&B and the A B juxtaposition to mean $_ ~~ A && $_ ~~ B
: > which is an intersection (sub)type of A and B.
:
: Is the A&B form a legal alternative for the juxtaposition?
Not in a signature. It's ambiguou
Trey Harris wrote:
Trey Harris writes:
> chromatic writes:
>> When you specify a type to constrain some operation, you specify that the
>> target entity must perform that role.
>
> That statement is very concise and direct. If the fuzziness I observed about
> the identity of the basic building bl
Larry Wall wrote:
But I'm still somewhat set against the notion of using logical ops to
do set theory. (Even if you put parens around them.)
Understandably so. Perhaps "(u)" and "(n)" would be better ASCII
equivalents for the union and intersection operators...
--
Jonathan "Dataweaver" Lang
On Saturday 28 October 2006 09:15, Larry Wall wrote:
> My initial inclination is to say that "where" clauses in a signature
> are only there for pattern matching, and do not modify the official
> type of the parameter within the function body. However, on a "subset"
> the "where" clause is there