[EMAIL PROTECTED] writes: : A single internal encoding which is opaque to the programmer Would Be Nice. We seem to be asking for contradictory things here. If it's truly opaque, the programmer shouldn't care whether it's polymorphic or monomorphic. I'm inclined to think the polymorphic solution will be more efficient. I could be wrong, of course. But if we write the interface right, we can swap in a monomorphic implementation at any point. Larry
- RFC 131 (v1) Internal String Storage to be Opaque Perl6 RFC Librarian
- Re: RFC 131 (v1) Internal String Storage to be Op... Bradley M. Kuhn
- Re: RFC 131 (v1) Internal String Storage to be Op... Jarkko Hietaniemi
- Re: RFC 131 (v1) Internal String Storage to b... Simon Cozens
- Re: RFC 131 (v1) Internal String Storage to be Op... Larry Wall
- Re: RFC 131 (v1) Internal String Storage to b... Simon Cozens
- Re: RFC 131 (v1) Internal String Storage to be Op... Bryan C . Warnock
- Re: RFC 131 (v1) Internal String Storage to be Op... Simon Cozens