Re: Template mixins: Why is the decision to mixin made at the call site?

Bill Baxter wrote: > On Fri, Aug 21, 2009 at 10:36 AM, div0 wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Not sure what the original choice was based on, but what you suggest >> looks wrong to me. You aren't necessarily using a template in order to >> mix it in somewhere. >> >> W

Re: Template mixins: Why is the decision to mixin made at the call site?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steven Schveighoffer wrote: > On Fri, 21 Aug 2009 13:54:38 -0400, div0 > wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Jarrett Billingsley wrote: >>> On Fri, Aug 21, 2009 at 1:36 PM, div0 wrote: >>> >>> That's what he's suggestin

Re: Template mixins: Why is the decision to mixin made at the call site?

On Fri, 21 Aug 2009 13:54:38 -0400, div0 wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jarrett Billingsley wrote: On Fri, Aug 21, 2009 at 1:36 PM, div0 wrote: That's what he's suggesting, and it does make sense. When you write a template, *either* it's meant to be used as a mixin,

Re: Template mixins: Why is the decision to mixin made at the call site?

div0 wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ary Borenszweig wrote: div0 wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jarrett Billingsley wrote: On Fri, Aug 21, 2009 at 1:36 PM, div0 wrote: That's what he's suggesting, and it does make sense. When you write a template,

Re: Template mixins: Why is the decision to mixin made at the call site?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ary Borenszweig wrote: > div0 wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Jarrett Billingsley wrote: >>> On Fri, Aug 21, 2009 at 1:36 PM, div0 wrote: >>> >>> That's what he's suggesting, and it does make sense. When you write a >>

Re: Template mixins: Why is the decision to mixin made at the call site?

div0 wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jarrett Billingsley wrote: On Fri, Aug 21, 2009 at 1:36 PM, div0 wrote: That's what he's suggesting, and it does make sense. When you write a template, *either* it's meant to be used as a mixin, *or* it's meant to be used some other wa

Re: Template mixins: Why is the decision to mixin made at the call site?

On Fri, Aug 21, 2009 at 10:36 AM, div0 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Chad J wrote: >> Regarding template mixins, I'm curious, why is the decision to mixin a >> template made at the call site and not at the declaration of the >> template/mixin? >> >> In other words, wh

Re: Template mixins: Why is the decision to mixin made at the call site?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jarrett Billingsley wrote: > On Fri, Aug 21, 2009 at 1:36 PM, div0 wrote: > > That's what he's suggesting, and it does make sense. When you write a > template, *either* it's meant to be used as a mixin, *or* it's meant > to be used some other way. Mi

Re: Template mixins: Why is the decision to mixin made at the call site?

On Fri, Aug 21, 2009 at 1:36 PM, div0 wrote: > Not sure what the original choice was based on, but what you suggest > looks wrong to me. You aren't necessarily using a template in order to > mix it in somewhere. > > With that syntax it looks like you can only use foo as a mixin. That's what he's s

Re: Template mixins: Why is the decision to mixin made at the call site?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chad J wrote: > Regarding template mixins, I'm curious, why is the decision to mixin a > template made at the call site and not at the declaration of the > template/mixin? > > In other words, why do we write > > template foo() > { >

Template mixins: Why is the decision to mixin made at the call site?

Regarding template mixins, I'm curious, why is the decision to mixin a template made at the call site and not at the declaration of the template/mixin? In other words, why do we write template foo() { // etc.. } mixin foo!(); instead of m