Set & Table hierarchy

[Mark S. Miller <mark>]

Date: Wed, 15 Nov 89 20:11:40 PST
   From: ravi (Ravi Pandya)

      Date: Tue, 14 Nov 89 12:23:56 PST
      From: mark (Mark S. Miller)

      What do the "mutable" & "immutable" messages to a ScruSet mean?  

   I meant them to mean asMuSet and asImmuSet, and I agree that they
   should be renamed as such. All three (Mu/Scru/Immu) should be defined
   in ScruSet so that they can be used polymorphically.  Likewise for
   tables.

Which of the following two equations hold:

Set * p = muSet (...);

1) p->asMuSet() === p

2) p->asMuSet() === p->asImmuSet()->asMuSet() === p->copy()

?  I would argue that the second is correct.


   A related issue is whether Mu's will support Immu protocol as well. I
   don't think that they need to -- you can just say
   x->asImmutable()->intersect(y).

Agreed.