std.typecons.Ref(T).opImplicitCastTo()

[Jonathan M Davis]

On Monday, April 02, 2012 09:37:04 Alex Rønne Petersen wrote:
> On 02-04-2012 07:32, Jonathan M Davis wrote:
> > On Monday, April 02, 2012 07:23:23 Alex Rønne Petersen wrote:
> >> On 02-04-2012 06:25, Jonathan M Davis wrote:
> >>> alias this is not supposed to be restricted such that you can only have
> >>> one
> >>> per type. That's a temporary, implementation problem. TDPL specifically
> >>> talks about having multiple alias thises per type.
> >>> 
> >>> - Jonathan M Davis
> >> 
> >> What is the reason it hasn't been realized yet?
> > 
> > I don't know. While we're getting closer to having everything in TDPL
> > implemented correctly each release, there's still plenty of stuff left to
> > do, and no one has tackled the alias this issue yet. I expect that it's
> > not an entirely easy thing to fix and that other stuff has been higher
> > priority.
> > 
> > http://d.puremagic.com/issues/show_bug.cgi?id=6083
> > 
> > The major thing being tackled this release has been const-correctness, and
> > it's not done yet (in spite of there now being a beta for 2.059). I
> > believe
> > that that's been one of Walter's major focuses this release cycle, and I
> > wouldn't really expect him to tackle anything else major until Object's
> > const- correctness been sorted out. Nothing is stopping someone else from
> > doing it, but no one has. Plenty of other stuff has been fixed though.
> > 
> > - Jonathan M Davis
> 
> To clarify, I mean to ask whether there are any design flaws in the
> strategy of having multiple alias this in one type, or whether it is
> purely an issue in the implementation (i.e. just plain hasn't been done
> yet)?

As far as I know, it's purely an implementation issue, but I don't know.

- Jonathan M Davis