You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coverage today: TypeScript/TSX, JavaScript/JSX, Rust, Python, Go. The next clean fits with mature grammars and nested named symbols are Java, C#, and Ruby.
I would not recommend this as a first issue for 2 reasons. Firstly, it is quite a complex issue and would touch a huge segment of the codebase, I have moved it to the backlog and will only be considering this enhancement if there is a real demand for it one day.
That being said. If you wish to contribute I recommend issue #45. Its got a much clearer scope and is a better way to get familiar with the fixture/test set up. Its about adding test coverage for Unicode identifiers and path edge cases: writing fixtures with non-ASCII symbol names across the language families and confirming resolution/hashing stays stable, plus checking that Windows-style paths fail with a clear parse error. It may even surface a real bug or two. Want to take that one?
Activity
ASUR12ZURVAN commentedon Jun 20, 2026
The topic, intrigued me but i wasn't able to understand the full issue. Can you explain it to me briefly, i would love to contribute.
Connorrmcd6 commentedon Jun 21, 2026
Hi @ASUR12ZURVAN , thanks for the interest!
I would not recommend this as a first issue for 2 reasons. Firstly, it is quite a complex issue and would touch a huge segment of the codebase, I have moved it to the backlog and will only be considering this enhancement if there is a real demand for it one day.
That being said. If you wish to contribute I recommend issue #45. Its got a much clearer scope and is a better way to get familiar with the fixture/test set up. Its about adding test coverage for Unicode identifiers and path edge cases: writing fixtures with non-ASCII symbol names across the language families and confirming resolution/hashing stays stable, plus checking that Windows-style paths fail with a clear parse error. It may even surface a real bug or two. Want to take that one?
ASUR12ZURVAN commentedon Jun 21, 2026
Hey @Connorrmcd6 , really thanks for the advice. i would take it and try to contribute, to the issue 45.