-
Notifications
You must be signed in to change notification settings - Fork 33
Need a hand? #119
Comments
Any help would be much appreciated. Unfortunately I currently don't find much time to spend on improving language-rust. Most open issues are "complicated", i.e. they're not simple grammar rules problems but need a deeper look into how atom packages work (which I unfortunately don't have). If you'd like to stay for a while and help to move things ahead, I could as well add you as a collaborator. We should just make sure to discuss bigger changes openly first and to have working specs all time to prevent regressions. #82 looks nice, but is missing some automated specs. It adds some lines to test.rs which was used for manually reviewing syntax highlighting before we had specs. |
Is this still the case @zargony ? |
Yes. I think I know Rust pretty well, but my knowledge of Atom’s JS internals is limited and RL keeps me busy, so I appreciate any help. |
|
That would be great, to further improve this project! :) |
Yes I, and all atom rust users, am interested in improvements (though overall it's still working pretty well). However, I don't have a lot of free time myself at the moment. Interestingly it looks like they'll also be official rust support for atom when they adopt the tree-sitter parsing system: https:/atom/language-rust. But who knows when that'll be. |
fyi atom/atom#18257 |
Thanks. Looks like there’s a tree-sitter based grammar for Rust now. |
@zargony
I'm working on
ide-rust
in conjunction with the Atom IDE and Rust Dev Tools movements.I have some pain points with
language-rust
and I was taking a look but it seems like at least one of them ( #82 ) has an open PR.I'd love to help you with adding syntax and improvements to the grammar here. Thoughts?
The text was updated successfully, but these errors were encountered: