Smarty registerClass() call with named (like PHP 8+) arguments

We can register class:

$smarty->registerClass("OptionSwitcher", "\My\App\OptionSwitcher");

and use it something like this:

{OptionSwitcher::html('switch_debug_mode', 'is_debug_mode_active') }

It works nice... but OptionSwitcher::html() method have more than two arguments:

public static function html(string $switcher_id = '', string $exposed_smarty_variable = '', string $on_text = 'YES', string $off_text = 'NO', string $css_tuning_class = '', string $request_uri = '', bool $is_enabled = true): string
    {
// ... 
}

If it is necessary to pass a different value for the is_enabled argument than the default value, you will need to list all the arguments preceding it, passing the desired values (or default values):

{OptionSwitcher::html('switch_debug_mode', 'is_debug_mode_active', 'YES', 'NO', '', '', false) }

... looks ugly

The way out of this is the named argument mechanism introduced in PHP 8: https://www.php.net/manual/en/functions.arguments.php#functions.named-arguments

array_fill(start_index: 0, count: 100, value: 50);

or, in my case:

// call
OptionSwitcher::html('switch_debug_mode', 'is_debug_mode_active', is_enabled: false)

Does Smart support such a mechanism at the templates? Like this:

{OptionSwitcher::html('switch_debug_mode', 'is_debug_mode_active', is_enabled: false) }

?

The issue names no files or tests. Start by locating Smarty's handling of registered-class calls and comparing its argument parsing with PHP 8 named arguments. Done means a template call using a named argument works while existing positional calls remain supported, with tests covering the example.