Wed, 22 Mar 2000 15:23:32 +0100 (MET), Bjorn Lisper <[EMAIL PROTECTED]> pisze:
> I think the cleanest solution is to add a method "hseq" to the Eval
> class, which is similar to seq but evaluates its first argument
> hyperstrictly before returning its second.
You mean "implicit Eval"? Then I would certainly not call this solution
"clean". Even the full polymophism of seq is considered controversial,
and the Eval class was explicit before.
It can be argued that since every type contains its bottom, there is a
natural seq for each type, and the implementation would probably use
uniform interface for evaluation of the head for all types anyway,
so seq is probably justified. But I can very hardly think about
hyperseq as fully polymorphic.
--
__("< Marcin Kowalczyk * [EMAIL PROTECTED] http://qrczak.ids.net.pl/
\__/ GCS/M d- s+:-- a22 C+++$ UL++>++++$ P+++ L++>++++$ E-
^^ W++ N+++ o? K? w(---) O? M- V? PS-- PE++ Y? PGP+ t
QRCZAK 5? X- R tv-- b+>++ DI D- G+ e>++++ h! r--%>++ y-
