-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's the state of this project? #416
Comments
The projects definetely need new blood. People that created it initially mostly moved on to other duties so not many updates are to be expected unless someone jumps in to take over maintenance. Considering that majority of the functionality is provided by other Eclipse bits which are still well maintained this shouldn't be too much effort for someone using Rust daily so can help on rust-analyzer side. |
It's a bit stale to be fair, unfortunately I haven't had much time to contribute. On a good note, I did get the up-to date version from I've been using JetBrains CLion on and off for Rust development too, lately. It's a polished experience but the lack of support for Rust-analyser and full-solution analysis is really upsetting. Their replacement for it, called "Inspections" are between unusable and counterproductive. |
Closing this one as it's not an issue in the codebase. |
I see there's been no updates on this repo since September 27th 2022, it's now 8th February 2023, I'm just wondering if this project is dead, needs new maintainers, etc?
Given that Rust is one of the most loved programming language (https://survey.stackoverflow.co/2022/#technology-most-loved-dreaded-and-wanted) and that Eclipse is the best free IDE with good embedded debugging support, it'd be really nice if Eclipse Corrosion was more frequently updated to fix outstanding issues.
On a day-to-day basis the main issues for me are the non-functioning outline and hover-over functionality due to Language Server Background job never completes, see rust-lang/rust-analyzer#10910 (comment)
The text was updated successfully, but these errors were encountered: