Stephan Seitz

We also had the artifact upload for situations like this one. I'll quickly add it to see whether the compiler actually has produced something.

@clason no, we only generated one aritfact! And we don't know from which OS. I forgot to add OS/CC name in the artifacts

No make parser. So probably a silent compilation/linkage failure of msvc

We updated the MSVC workflow recently

This will be better supported in https://github.com/neovim/neovim/pull/17099 , you will then get `(import_statement)* @import` grouped in the query results. We still have our old `TSRange` interface but no modern directives...

We still haven't re-enabled the async mode. There is no reason why Neovim startup should take longer just because we are still working on the syntax highlighting. Also there is...

You will only have an overhead on the first open of the file both with InstallFromGrammar and normal (every next file query parsing will be cached). Your timings were with...

You mean you closed and opened Neovim a few times? Could this then be about loading the file from filesystem. This shouldn't make more than a few milliseconds difference. Do...

This should probably apply only to strings just before functions and classes (and probably all kinds of strings not only triple_quoted)

Restricted this to top-level strings. Is this found also on struct/module level?