On Sat, Jul 31, 2010 at 21:17, Lutger wrote:
> Jason Spencer wrote:
>
> > == Quote from Philippe Sigaud (philippe.sig...@gmail.com)'s article
> >> --0016e6d58a039d35e2048c9aa7e2
> >>
> >> I thought they could only be symbols. That is, an alias is a 'link',
> > a sort
> >> of pointer to a symbol:
Jason Spencer wrote:
> == Quote from Philippe Sigaud (philippe.sig...@gmail.com)'s article
>> --0016e6d58a039d35e2048c9aa7e2
>>
>> I thought they could only be symbols. That is, an alias is a 'link',
> a sort
>> of pointer to a symbol: a template name, a module name, a function
>> name, etc.
>
>
== Quote from Philippe Sigaud (philippe.sig...@gmail.com)'s article
> --0016e6d58a039d35e2048c9aa7e2
>
> I thought they could only be symbols. That is, an alias is a 'link',
a sort
> of pointer to a symbol: a template name, a module name, a function
> name, etc.
Whatever confidence you inspired by
On Thu, Jul 29, 2010 at 22:40, Jason Spencer wrote:
> In writing templates that make heavy use of alias parameters, does
> anyone else feel uneasy about whether the caller will pass a type, a
> value, or a schmoo?
I thought they could only be symbols. That is, an alias is a 'link', a sort
of po
Jason Spencer:
> In writing templates that make heavy use of alias parameters, does
> anyone else feel uneasy about whether the caller will pass a type, a
> value, or a schmoo?
Normally D is a mostly statically typed language (objects have a dynamic type),
but sometimes template juggling is purel
In writing templates that make heavy use of alias parameters, does
anyone else feel uneasy about whether the caller will pass a type, a
value, or a schmoo? I'm having a hard time getting my head around
how wide-open aliases are and trying to resist the urge to put in
thousands of static asserts to
