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

2012-04-02 Thread Alex Rønne Petersen
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

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

2012-04-02 Thread 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

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

2012-04-01 Thread James Miller
On 31 March 2012 06:28, Jonathan M Davis jmdavisp...@gmx.com wrote: it also has opDot, which is being removed from the language. Out of curiosity, what was opDot? -- James Miller

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

2012-04-01 Thread Alex Rønne Petersen
On 30-03-2012 19:28, Jonathan M Davis wrote: On Friday, March 30, 2012 16:27:44 simendsjo wrote: Is opImplicitCastTo a planned feature? It's only used in this type as I can see, and it doesn't add implicit casting. It's been discussed, but I don't think that it's ever been agreed upon. In

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

2012-04-01 Thread Jonathan M Davis
On Monday, April 02, 2012 05:41:00 Alex Rønne Petersen wrote: On 30-03-2012 19:28, Jonathan M Davis wrote: On Friday, March 30, 2012 16:27:44 simendsjo wrote: Is opImplicitCastTo a planned feature? It's only used in this type as I can see, and it doesn't add implicit casting. It's

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

2012-04-01 Thread Jonathan M Davis
On Monday, April 02, 2012 15:36:01 James Miller wrote: On 31 March 2012 06:28, Jonathan M Davis jmdavisp...@gmx.com wrote: it also has opDot, which is being removed from the language. Out of curiosity, what was opDot? An overload of the dot operator. So, if you had A a = foo(); a.func();

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

2012-04-01 Thread Alex Rønne Petersen
On 02-04-2012 06:25, Jonathan M Davis wrote: On Monday, April 02, 2012 05:41:00 Alex Rønne Petersen wrote: On 30-03-2012 19:28, Jonathan M Davis wrote: On Friday, March 30, 2012 16:27:44 simendsjo wrote: Is opImplicitCastTo a planned feature? It's only used in this type as I can see, and it

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

2012-04-01 Thread Jonathan M Davis
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

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

2012-03-30 Thread simendsjo
Is opImplicitCastTo a planned feature? It's only used in this type as I can see, and it doesn't add implicit casting.

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

2012-03-30 Thread Jonathan M Davis
On Friday, March 30, 2012 16:27:44 simendsjo wrote: Is opImplicitCastTo a planned feature? It's only used in this type as I can see, and it doesn't add implicit casting. It's been discussed, but I don't think that it's ever been agreed upon. In theory, alias this is meant to deal with