Re: RFC 159 (v1) True Polymorphic Objects

Damian Conway <damian@conway.org> writes:
>
>
>BTW, this is not just theoretical yearnings. I have written three modules
>in the past year that do not work as well as they could, simply because it
>is not possible to overload && and ||.
>
>Damian

I have one too.


-- 
Nick Ing-Simmons <nik@tiuk.ti.com>
Via, but not speaking for: Texas Instruments Ltd.

• Re: RFC 159 (v1) True Polymorphic Objects by Tom Christiansen
• Re: RFC 159 (v1) True Polymorphic Objects by Nathan Wiger
• Re: RFC 159 (v1) True Polymorphic Objects by Tom Christiansen
• Re: RFC 159 (v1) True Polymorphic Objects by Tom Christiansen
• Re: RFC 159 (v1) True Polymorphic Objects by Bennett Todd
• Re: RFC 159 (v1) True Polymorphic Objects by Jeremy Howard
• Re: RFC 159 (v1) True Polymorphic Objects by Tom Christiansen
• RFC 159 (v1) True Polymorphic Objects by Perl6 RFC Librarian
• Re: RFC 159 (v1) True Polymorphic Objects by Damian Conway
• Re: RFC 159 (v1) True Polymorphic Objects by Nick Ing-Simmons
• Re: RFC 159 (v1) True Polymorphic Objects by Damian Conway
• Re: RFC 159 (v1) True Polymorphic Objects by Piers Cawley
• Re: RFC 159 (v1) True Polymorphic Objects by Nathan Wiger
• Re: RFC 159 (v1) True Polymorphic Objects by Jonathan Scott Duff
• Re: RFC 159 (v1) True Polymorphic Objects by Nathan Wiger
• Re: RFC 159 (v1) True Polymorphic Objects by Nathan Wiger
• Re: RFC 159 (v1) True Polymorphic Objects by David L. Nicol