Darren Duncan schreef: > What I propose concerning non-premature === optimizing is a system > where, at any time that two appearances of the same immutable value > are compared with ===, they are immediately consolidated into a > single appearance.
That should only be done voluntarily. A bit like memoization. Something else: An immutable composite value can have unfinalized parts. Finalizing them for the sake of a deep comparison, can hurt performance. Does a lazy system need something like 'undecided' or 'NaB' (not-a-boolean)? -- Groet, Ruud
