Re: ignorance: customizable immutables?

> Are there any approaches people like to use to get immutables that
> respect whatever customization has been done -- some way to assemble
> components and then still be able to frob() them and get a new
> immutable copy that retains the customizations? Concisely, robustly? I
> mean in any programming language.

So, like, a composite object, that took on the unified type of the
pieces, and then proxied all 'set' calls so that it could call clone()
on each of the unchanged parts, to produce the final new version of
itself?

-- 
You received this message because you are subscribed to the Google Groups "scala-language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.