vim.vim: confusion for function return types starting on another line

[zzzyxwvut]

Steps to reproduce

When the function signature is long and its return type is
started on another line, highlighting for the type and the
function body is gone.

There is also some premature recognition of vimReturnType
for dict<...> in TestC*. TestD* are fine.

vim9script

def TestA______________________________________________________________():
    \ void
enddef

def TestB____(result: dict<list<number>>, fs: list<func(number): number>):
    \ void
enddef

def TestC____(maybe: bool, F: func(): dict<func(number): number>): func():
	\ void
    return () => {
    }
enddef

def TestD____(fs: list<func(): dict<func(number): bool>>): func(): func():
	\ void
    return () => () => {
    }
enddef

class Tests
    def TestA__________________________________________________________():
	\ void
    enddef

    def TestB(result: dict<list<number>>, fs: list<func(number): number>):
	\ void
    enddef

    def TestC(maybe: bool, F: func(): dict<func(number): number>): func():
	    \ void
	return () => {
	}
    enddef

    def TestD(fs: list<func(): dict<func(number): bool>>): func(): func():
	    \ void
	return () => () => {
	}
    enddef
endclass

defcompile

Expected behaviour

Syntax highlighting should allow for function return types
starting on the next line.

Version of Vim

v9.1.0274

Environment

GNU/Linux Debian (testing/trixie)

Logs and stack traces

No response

[zzzyxwvut]

Ping @dkearns.

[dkearns]

I can fix this particular issue, but it's a game of whack-o-mole. We really need a syn-skip-group as line continuations and line-continuation comments can appear anywhere.

I was bit surprised to see that Vim can't parse the return type without a line continuation. @yegappan does that seem right to you?

I've noted the type highlighting as well, thanks.

[yegappan]

I was bit surprised to see that Vim can't parse the return type without a line continuation. @yegappan does that seem right to you?

No. This is a bug. Requiring a line continuation after a ":" for the return type doesn't seem correct.

[zzzyxwvut]

Note that you can't help but escape each type when hard put
to it.