`set ... as ...` is not adequacy

[Koc]

# SQL
SELECT CONCAT('foo', 'bar') AS gg

# Twig
{% set gg as 'foo' ~ 'bar' %}

As you see - variable name and value of this variable in Twig swapped.

So I propose: a) provide is {% set gg is 'foo' ~ 'bar' %} b) swap varible name and variable value.

Yes, I know that it will break backward compatibility but it will add more of the adequacy.

[fabpot]

You are totally right. I don't want to swap variable name and the value, as it won"t make sense for the block tag:

{% block title as 'title' %} -> {% block 'title' as title %} won't be easy to parse

So, I think changing as to is is the best thing to do. Any other idea for the word in between? "is" looks quite fine but I would have preferred another adjective if possible.

[Koc]

no, I haven't any other idea for word between, Maybe eq or equal, but it looks as compare. Or does it possible use = ?)

[fabpot]

ok, I think I will use = as this is what Jinja uses.

[fabpot]

changed as to = for the set tag and removed the need for as in short-notation of the block tag (closed by 8809a1cab12202e9baccc26e9a6fea2da0a956a7)

[jmikola]

{% set gg to 'foo' %} would have worked, too, but = is perfectly clear