Re: [tosca] New syntax for function calls

Right, that proposal was weird for exactly that reason -- treating a name (a non-value) as a value. That's part of the reason I added a second version of that proposal, of using the "aliases" keyword in which actual values are expected. Can you show us an example from Unfurl of using "q"?

On Wed, Mar 17, 2021 at 7:06 AM adam souzis <adam@souzis.com> wrote:

Good point, there isn't any ambiguity if there's a leading escape character. I was thing more about your example for node templates, e.g.Â
"{ concat: [ site-, { get_variable: [ SITE, name ] } ] }"

How do you know it'sÂnot a template with that name?

BTW, for the issue you brought up about functions, in Unfurl I have a function called "q" (for "quote") that resolves to its value. That solves the problem in a similarÂway but doesn't introduce any new syntax.

tosca message