Empowering everyone to build reliable and efficient software.
Go to file
bors[bot] 3d8a0982a1 Merge #866
866: Implement basic support for Associated Methods r=flodiebold a=vipentti

This is my attempt at learning to understand how the type inference works by adding basic support for associated methods. Currently it does not resolve associated types or constants. 

The basic idea is that `Resolver::resolve_path` returns a new `PathResult` type, which has two variants, `FullyResolved` and `PartiallyResolved`, fully resolved matches the previous behavior, where as `PartiallyResolved` contains the `PerNs<Resolution` in addition to a `segment_index` which contains the index of the segment which we failed to resolve. This index can then be used to continue inference in `infer_path_expr` using the `Type` we managed to resolve.

This changes some of the previous apis, so looking for feedback and suggestions.

This should enable fixing #832

Co-authored-by: Ville Penttinen <villem.penttinen@gmail.com>
2019-02-22 19:58:22 +00:00
.cargo Add cargo jinstall-lsp as a shorthand to include jemalloc support 2019-01-29 17:02:06 +00:00
.vscode Config for raLspServerPath will be overwritten if __RA_LSP_SERVER_DEBUG is set 2019-01-19 15:36:54 +03:00
crates Merge #866 2019-02-22 19:58:22 +00:00
editors Use named multiline Problem Matcher 2019-02-18 13:12:54 -05:00
.gitignore Add .vscode/settings.json to .gitignore 2019-01-19 15:37:25 +03:00
.travis.yml fix verification on CI 2019-01-27 02:30:54 +03:00
ARCHITECTURE.md Add cargo jinstall-lsp as a shorthand to include jemalloc support 2019-01-29 17:02:06 +00:00
bors.toml don't gate on appveyor 2018-10-09 19:06:05 +03:00
Cargo.lock Update lsp-types and backtrace 2019-02-21 10:07:14 -05:00
Cargo.toml update salsa 2019-01-15 15:06:45 +03:00
CONTRIBUTING.md brush up docs 2018-10-15 01:05:18 +03:00
DEBUGGING.md Removed gif 2019-01-19 15:36:58 +03:00
guide.md add illustrations 2019-01-21 10:27:01 +02:00
LICENSE-APACHE Licenses 2018-01-10 22:47:04 +03:00
LICENSE-MIT Licenses 2018-01-10 22:47:04 +03:00
README.md update readme to point to the WG 2019-02-12 17:55:02 +03:00
ROADMAP.md don't mention beta channel Rust in ROADMAP 2018-12-28 14:38:27 -08:00
rustfmt.toml enable "small heuristics" 2019-02-08 14:49:26 +03:00

Rust Analyzer

Build Status

Rust Analyzer is an experimental modular compiler frontend for the Rust language. It is a part of a larger rls-2.0 effort to create excellent IDE support for Rust. If you want to get involved, check rls-2.0 working group repository:

https://github.com/rust-analyzer/WG-rls2.0

Work on the Rust Analyzer is sponsored by

Ferrous Systems

Quick Start

Rust analyzer builds on Rust >= 1.31.0 and uses the 2018 edition.

# run tests
$ cargo test

# show syntax tree of a Rust file
$ cargo run --package ra_cli parse < crates/ra_syntax/src/lib.rs

# show symbols of a Rust file
$ cargo run --package ra_cli symbols < crates/ra_syntax/src/lib.rs

# install the language server
$ cargo install-lsp
or
$ cargo install --path crates/ra_lsp_server

See these instructions for VS Code setup and the list of features (some of which are VS Code specific).

Debugging

See these instructions on how to debug the vscode extension and the lsp server.

Getting in touch

We are on the rust-lang Zulip!

https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frls-2.2E0

Contributing

See CONTRIBUTING.md and ARCHITECTURE.md

Supported LSP features

General

Workspace

Text Synchronization

Diagnostics

Lanuguage Features

License

Rust analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.