>>>>> "AS" == Ariel Scolnicov <[EMAIL PROTECTED]> writes:
AS> They're going to be useful to a tiny minority of users: math folks
AS> whose application matches the use of a hash-based implementation.
AS> (Actually, all uses I've seen of set datatypes were strictly outside
AS> mathematics, but that doesn't alter your argument or mine). The
AS> problem is that the desired semantics (in the sense, e.g., of
AS> worst-case, average-case, and "my-case" complexity) of the "set"
AS> datatype vary greatly with application.
Tiny minority? I'm no mathematician, but I've used set operations to
avoid redoing known work. And I've used hashes simply because I have
no other 'lazy' choice. But the code becomes harder to read.
>From a conceptual level, when looking at the code (not the surrounding
application) I'm no longer working with the data, but rather with a
side effect.
<chaim>
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
