-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Add support for the Rust programming language #1888
Conversation
Reviewed 1 of 3 files at r1. README.md, line 351 [r1] (raw file): README.md, line 897 [r1] (raw file): README.md, line 898 [r1] (raw file): Comments from the review on Reviewable.io |
Reviewed 1 of 1 files at r2. README.md, line 51 [r2] (raw file): Comments from the review on Reviewable.io |
Reviewed 2 of 3 files at r1. Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 4 unresolved discussions. README.md, line 51 [r2] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 4 unresolved discussions. README.md, line 898 [r1] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 5 unresolved discussions. README.md, line 173 [r2] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 7 unresolved discussions. README.md, line 51 [r2] (raw file): Joe can pick whichever he prefers here. I'd go with racerd, but again, I don't really care. README.md, line 892 [r2] (raw file): Also, "a configuration is needed" sounds a bit weird. How about:
README.md, line 1130 [r2] (raw file): For Rust, people will just use GoTo anyway. README.md, line 1154 [r2] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 4 unresolved discussions. README.md, line 51 [r2] (raw file): Whether README.md, line 173 [r2] (raw file): README.md, line 892 [r2] (raw file): README.md, line 1130 [r2] (raw file): Comments from the review on Reviewable.io |
Should I document the Review status: 1 of 3 files reviewed at latest revision, 4 unresolved discussions. Comments from the review on Reviewable.io |
Reviewed 2 of 2 files at r3. README.md, line 51 [r2] (raw file):
Is for that reason that initially I proposed:
So we would both inform the user that the engine used is Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 4 unresolved discussions. README.md, line 51 [r2] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 4 unresolved discussions. README.md, line 51 [r2] (raw file): Comments from the review on Reviewable.io |
README.md, line 51 [r2] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 4 unresolved discussions. README.md, line 51 [r2] (raw file): Comments from the review on Reviewable.io |
It is worth documenting it I think because we have no other place to do so conveniently, and otherwise it's just magic. But it shouldn't block merging in my opinion :) Remember some part of vim ethos is all about good and complete docs. :) With that LGTM. Reviewed 1 of 1 files at r2, 2 of 2 files at r3. README.md, line 51 [r2] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 4 unresolved discussions. README.md, line 51 [r2] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 1 unresolved discussion. Comments from the review on Reviewable.io |
@homu r+ Review status: all files reviewed at latest revision, 1 unresolved discussion. Comments from the review on Reviewable.io |
📌 Commit 210db41 has been approved by |
⚡ Test exempted - status |
Add support for the Rust programming language Support for the Rust programming language is added using ycmd's racerd completer. This PR contains documentation for using the Rust completer and an update to the ycmd submodule. ## TODO - [x] Update ycmd submodule once ycm-core/ycmd#268 lands <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/valloric/youcompleteme/1888) <!-- Reviewable:end -->
Wohoo, this is awesome! Thanks a lot to all involved! :) |
Support for the Rust programming language is added using ycmd's racerd completer. This PR contains documentation for using the Rust completer and an update to the ycmd submodule.
TODO