Skip to content
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

Tracking issue for the Rust Language Server #31548

Closed
alexcrichton opened this issue Feb 11, 2016 · 10 comments
Closed

Tracking issue for the Rust Language Server #31548

alexcrichton opened this issue Feb 11, 2016 · 10 comments
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue.

Comments

@alexcrichton
Copy link
Member

Tracking issue for rust-lang/rfcs#1317

(to be filled in by @nrc...)

@alexcrichton alexcrichton added A-tools B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. labels Feb 11, 2016
@archshift
Copy link
Contributor

Has work started on this yet?

@nrc
Copy link
Member

nrc commented Mar 21, 2016

@archshift no. It is low priority for now until there is concrete progress with incremental compilation (perhaps mid 2016).

@pyfisch
Copy link
Contributor

pyfisch commented Jun 28, 2016

The Language Server Protocol is "a common protocol for languages" and is supported Red Hat, Codenvy and Microsoft. If this becomes a standard protocol it would be great if Rust used it.

@lilianmoraru
Copy link

@pyfisch Came here to post this 😄

@mfarrugi
Copy link

Kythe also has a similar, though less targeted goal than the 'Language Server Protocol'.

@Marwes
Copy link
Contributor

Marwes commented Jul 31, 2016

Added basic language server support for my own language (written in Rust). The language server API is not complete yet but I would be happy to separate out the language agnostic parts to its own crate if that would be useful.

https://github.com/Marwes/gluon_language-server

@bruno-medeiros
Copy link

Added basic language server support for my own language (written in Rust). The language server API is not complete yet but I would be happy to separate out the language agnostic parts to its own crate if that would be useful.

https://github.com/Marwes/gluon_language-server

Ha, I had just started very similar work last week: https://github.com/RustDT/RustLSP
RustLSP is meant to be just the LSP protocol, not tied to any actual language engine.

I'm hoping later to actually provide a basic Rust language server, by integrating Racer, Rainicorn, maybe even cargo build and rustw to the LSP protocol.

@Marwes
Copy link
Contributor

Marwes commented Aug 2, 2016

@bruno-medeiros I finished making the rest of the serializing structures yesterday (barring a mistake here or there), if you want I can move them to a crate and submit to crates.io if you want to skip the tedious part of the server.

@bruno-medeiros
Copy link

@Marwes Thanks, but I ended up adding it myself, since I wanted to review the whole protocol document, as well as review the underlying Rust code ( https://github.com/RustDT/RustLSP/blob/master/src/lsp.in.rs ). I did look at your code for some ideas, though. Speaking of, doesn't serde have a built-in way to (de)serialize numeric enums? 😮 I'm surprised we'd have to write our own code for that.

@brson brson added the B-unstable Blocker: Implemented in the nightly compiler and unstable. label Mar 1, 2017
@alexcrichton alexcrichton added T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. and removed T-tools labels May 22, 2017
@Mark-Simulacrum Mark-Simulacrum added C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. and removed C-enhancement Category: An issue proposing an enhancement or a PR with one. C-feature-request Category: A feature request, i.e: not implemented / a PR. labels Jul 22, 2017
@alexcrichton
Copy link
Member Author

I suspect that this tracking issue isn't really tracking much any more, so closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests