Suggestion: {namspace} compile tag

I experience quite frequently that class constants or enums have to be used in templates, e.g. in but not limited to if-conditions. These constants are typically located in namespaces.

Smarty templates for now reside in the root namespace, requiring to use absolute paths. Quite often all constants are from the same namespace, so that a {namespace} tag could make the template easier to handle, kind of this:

{namespace Foo\Bar\Baz}

{if $item->getSomeProperty() === ItemProperty::SomeValue}
   <p>this</p>
{elseif $item->getSomeProperty() === ItemProperty::SomeOtherValue}
   <p>that</p>
{elseif ...}
{else}
  <p class="warning">some property is not valid</p>
{/if}

{/namespace}

The issue names no files, tests, or entry points. Start by locating Smarty’s template compilation and tag-handling paths, then determine how the proposed {namespace} block should affect constant resolution. Done means the syntax and its behavior are defined and validated against the constant comparisons shown in the example.