New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vim.vim: confusion for function return types starting on another line #14442
Comments
Ping @dkearns. |
I can fix this particular issue, but it's a game of whack-o-mole. We really need a 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. |
No. This is a bug. Requiring a line continuation after a ":" for the return type doesn't seem correct. |
Note that you can't help but escape each type when hard put |
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<...>
inTestC*
.TestD*
are fine.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
The text was updated successfully, but these errors were encountered: