Re: Combining mutable objects with const references

Paul Rubin:
> In principle that is true; in practice, functional language systems
> tend to provide special data structures that allow programming in a
> non-mutating style while minimizing copying.

But is that because functional programmers are desperate to have the
persistence quality, or because there is simply no other way! To quote
Chris Okasaki, "...functional programming's stricture against
destructive updates (assignements) is a staggering handicap,
tantamount to confiscating a master chef's knives." :) If there is a
situation where persistence is required and can only be achieved
efficiently ("minimizing copying") with a special data structure, then
the imperative programmer can use that special data structure. He
always has as many options as the functional programmer, structure-
wise.