It's true in the sense that the features like jump-to-definition/find-usage are accurate. This is especially important around overloaded methods and parameterized types.
I wonder why this feature hasn’t attracted much attention:
21 days ago | 1 points | https://news.ycombinator.com/item?id=20170908
20 days ago | 4 points | https://news.ycombinator.com/item?id=20174715
19 days ago | 2 points | https://news.ycombinator.com/item?id=20183253
18 days ago | 2 points | https://news.ycombinator.com/item?id=20193151
15 days ago | 2 points | https://news.ycombinator.com/item?id=20216782
14 days ago | 2 points | https://news.ycombinator.com/item?id=20227589
2 days ago | 1 points | https://news.ycombinator.com/item?id=20327128
3 hours ago | 12 points | https://news.ycombinator.com/item?id=20348641
Not sure if it's only me. I have not ever used jump-to-definition feature on my editor. 95% of the time I just use search. But in case of Github web, it makes sense because their search feature isn't on par with local text editors.
Very cool! I wonder why they wrote their own source code analyzer instead of building off of the language servers that already exist: https://langserver.org/
It's true in the sense that the features like jump-to-definition/find-usage are accurate. This is especially important around overloaded methods and parameterized types.
A few days back, we recently launched parameter hints (blog: https://news.ycombinator.com/item?id=20320481) and type info (tweet: https://twitter.com/tanin/status/1145502393708081152).
We're looking for private beta users. Please let us know if anyone is interested :)