defstruct, and the :named option

[Scott E. Fahlman <Fahlman@CMU-CS-C>]

The solution you propose for the :named problem looks to me like the old
"cycle of reincarnation": the "primitives" grow more and more hair,
until pretty soon someone decides that it would be nice to have a
portable implementation of them, if only someone would define the right
primitives.  If we're going to put in all the stuff you suggest, we
might as well just say that DEFSTRUCT itself is a primitive that works
by implementation-dependent magic and let it go at that.  The original
pont was to add one tiny operation so that all the rest of DEFSTRUCT
could be portable.

-- Scott