Inability to dup/~ for const arrays of class objects

[Jonathan M Davis]

On Tuesday, May 28, 2013 23:03:10 Steven Schveighoffer wrote:
> On Tue, 28 May 2013 22:57:50 -0400, Jonathan M Davis <jmdavisProg at gmx.com>
> 
> wrote:
> > Every time that this comes up and Walter comments on it, he makes a
> > point of
> > saying that it's _not_ a syntax issue.
> 
> I remember differently, but maybe you are right. Haven't the time to look
> back.
> 
> But even if he *does* say that, I think it's more that we haven't found
> the *right* syntax.
>
> It's certainly only a syntax issue from a specification perspective, there
> is nothing inherently difficult about the underlying details.

It's primarily an implementation issue. As far as the spec itself goes, it 
shouldn't be a problem. As far as the spec goes, it's pretty much just a 
question of picking a good syntax. But getting that to work with the compiler 
when it doesn't differentiate between the class object and the reference to it 
in the type system isn't necessarily easy. As I recall, that was the core of 
what caused Walter so many problems when he worked on it in the past.

- Jonathan M Davis