aboutsummaryrefslogtreecommitdiffstats
path: root/lua
diff options
context:
space:
mode:
authorFredrik Ekre <ekrefredrik@gmail.com>2024-11-22 16:51:33 +0100
committerChristian Clason <ch.clason+github@icloud.com>2024-11-23 11:10:05 +0100
commit3f377c07390cd2a79de237ff00946a51d4d8c2a8 (patch)
treefc438a7179c448c61fa65fddd4c9efdf5e6484a4 /lua
parentfix(astro): highlight self-closing component tags (diff)
downloadnvim-treesitter-3f377c07390cd2a79de237ff00946a51d4d8c2a8.tar
nvim-treesitter-3f377c07390cd2a79de237ff00946a51d4d8c2a8.tar.gz
nvim-treesitter-3f377c07390cd2a79de237ff00946a51d4d8c2a8.tar.bz2
nvim-treesitter-3f377c07390cd2a79de237ff00946a51d4d8c2a8.tar.lz
nvim-treesitter-3f377c07390cd2a79de237ff00946a51d4d8c2a8.tar.xz
nvim-treesitter-3f377c07390cd2a79de237ff00946a51d4d8c2a8.tar.zst
nvim-treesitter-3f377c07390cd2a79de237ff00946a51d4d8c2a8.zip
fix(julia): treat :: as operator in type contexts
This patch captures `::` as `@operator` within `(unary_typed_expression)` and `(typed_expression)`. These should be the only two cases that the parser can emit when encountering `::` in the source, but as a fallback it is still captured as `@punctuation` in all other cases. The reasons for capturing `::` as an operator are i) the close relation with the other type-operators `<:` and `>:` and ii) the fact that it is treated as an operator by the Julia parser, just like `<:` and `>:`.
Diffstat (limited to 'lua')
0 files changed, 0 insertions, 0 deletions