Open JosephTLyons opened 3 days ago
@ghivert
To expand a bit, I think the syntax highlighting should help the reader to easily distinguish the context. When you encounter something like function_call()
or namespace.function_call()
, having them highlighted as function call would help, because that's the information you want to transmit to your reader. Thanks to tree sitter, we can even highlight pieces of code like data |> namespace.function_call
correctly. We can sometimes have false positive: when writing data |> struct.field
, field
will be highlighted as a function call even if it's not a function, but the LSP will trigger a warning. I think it's safe to consider that most of the time, we're spending time to read code, and because of the nature of Gleam, the code will be correct (thanks to the compiler). As such, it would make sense to favour easing of reading.
I'm curious to hear your opinions here. Of course, I'd be happy to open a proper pull request if we agree on this. 🙂
I updated the link and made it known the text came from you.
This issue was moved from the zed repository, originally filed by @ghivert: