Me:
>> 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.
Marcin 'Qrczak' Kowalczyk:
>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.
I don't know about full polymorphism (I guess hseq would not work well for
function-typed arguments, for instance), but I know there are situations
where it can be important from a practical perspective to add varying
degrees of strictness explicitly. Then I think the cleanest solution is to
have explicit operations which give you this, with a clearly stated
semantics, rather than the "x==x" kind of hack.
Björn Lisper
