Bjørn Erik Pedersen a03c631c42 Rework template handling for function and map lookups ... This is a big commit, but it deletes lots of code and simplifies a lot. * Resolving the template funcs at execution time means we don't have to create template clones per site * Having a custom map resolver means that we can remove the AST lower case transformation for the special lower case Params map Not only is the above easier to reason about, it's also faster, especially if you have more than one language, as in the benchmark below: ``` name old time/op new time/op delta SiteNew/Deep_content_tree-16 53.7ms ± 0% 48.1ms ± 2% -10.38% (p=0.029 n=4+4) name old alloc/op new alloc/op delta SiteNew/Deep_content_tree-16 41.0MB ± 0% 36.8MB ± 0% -10.26% (p=0.029 n=4+4) name old allocs/op new allocs/op delta SiteNew/Deep_content_tree-16 481k ± 0% 410k ± 0% -14.66% (p=0.029 n=4+4) ``` This should be even better if you also have lots of templates. Closes #6594		2019-12-12 10:04:35 +01:00
..
go_templates	Rework template handling for function and map lookups	2019-12-12 10:04:35 +01:00
templatefuncRegistry_test.go	tests: Convert from testify to quicktest	2019-08-12 13:26:32 +02:00
templatefuncsRegistry.go	tpl: Fix golint godoc issues	2018-09-07 08:25:51 +02:00