On Thu, 31 May 2012 17:42:05 +0200, Sönke Ludwig
Do you think its still worth to make this kind of parameter grouping
once the normal res.render!(templ, a, b, c, d) is used instead of
Yes, yes, yes :)
Since the parameters of a template are effectively defined by the
template just like they are defined for a function, I thought that
direct passing of them was ok. Or, better put, to me the tradeoff
between understandability and terseness of the code is slightly in favor
of explicit parameter passing.
But the order of the parameters is important if you pass around parameters.
I believe it will be a maintenance nightmare when you try to
add/change/remove parameters in the future.
..but to be more constructive - with DMD 2.060 the following simple (*)
scheme without Variant should also work:
// inject library:
alias Injectors First; alias Injectors[1 .. $] Rest; alias First!(Rest) injectReverse;
void reqInjector(alias Next, Vars...)(HttpServerRequest req,
Next!(Vars, req)(req, res);
@property auto inject(alias Page, Injectors...)()
return &injectReverse!(Injectors, reqInjector, Page);
void authInjector(alias Next, Vars...)(HttpServerRequest req,
string userinfo; Next!(Vars, userinfo)(req, res);
void somethingInjector(alias Next, Vars...)(HttpServerRequest req,
string something_else; Next!(Vars, something_else)(req, res);
void page(VARS...)(HttpServerRequest req, HttpServerResponse res)
listenHttp(new HttpServerSettings, inject!(page, authInjector,
(*) Actually this template stuff regularily makes my brain hurt...
Pretty much what I came up with, but when I tried to "clean" it up, I
ended up having to use string mixins to avoid several dmd bugs.. How I
long for the day dmd-just-works(TM)
I really like this solution, and will steal it if you don't add it to vibe