Quasi-literals for templating?

Axel Rauschmayer axel at rauschma.de
Wed Jun 15 08:36:55 PDT 2011

> The point is that the callSiteId captures all the literal/constant/loop-invariant parts of the quasi, both raw and cooked ("expandedLP"). The remaining quasi handler parameters are the necessarily variable, evaluated-at-runtime substitution expression results.

That makes sense. The ID then allows one to do caching. But I don’t see how the same quasi-literal can be “invoked” multiple times.

Dr. Axel Rauschmayer

axel at rauschma.de

home: rauschma.de
blog: 2ality.com

More information about the es-discuss mailing list