3d8a0982a1
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> |
||
---|---|---|
.cargo | ||
.vscode | ||
crates | ||
editors | ||
.gitignore | ||
.travis.yml | ||
ARCHITECTURE.md | ||
bors.toml | ||
Cargo.lock | ||
Cargo.toml | ||
CONTRIBUTING.md | ||
DEBUGGING.md | ||
guide.md | ||
LICENSE-APACHE | ||
LICENSE-MIT | ||
README.md | ||
ROADMAP.md | ||
rustfmt.toml |
Rust Analyzer
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
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
- workspace/workspaceFolders
- workspace/didChangeWorkspaceFolders
- workspace/didChangeConfiguration
- workspace/configuration
- workspace/didChangeWatchedFiles
- workspace/symbol
- workspace/executeCommand
apply_code_action
- workspace/applyEdit
Text Synchronization
- textDocument/didOpen
- textDocument/didChange
- textDocument/willSave
- textDocument/willSaveWaitUntil
- textDocument/didSave
- textDocument/didClose
Diagnostics
Lanuguage Features
- textDocument/completion
- open close: false
- change: Full
- will save: false
- will save wait until: false
- save: false
- completionItem/resolve
- resolve provider: none
- trigger characters:
:
,.
- textDocument/hover
- textDocument/signatureHelp
- trigger characters:
(
,,
,)
- textDocument/declaration
- textDocument/definition
- textDocument/typeDefinition
- textDocument/implementation
- textDocument/references
- textDocument/documentHighlight
- textDocument/documentSymbol
- textDocument/codeAction
- rust-analyzer.syntaxTree
- rust-analyzer.extendSelection
- rust-analyzer.matchingBrace
- rust-analyzer.parentModule
- rust-analyzer.joinLines
- rust-analyzer.run
- rust-analyzer.analyzerStatus
- textDocument/codeLens
- textDocument/documentLink
- documentLink/resolve
- textDocument/documentColor
- textDocument/colorPresentation
- textDocument/formatting
- textDocument/rangeFormatting
- textDocument/onTypeFormatting
- first trigger character:
=
- more trigger character
.
- textDocument/rename
- textDocument/prepareRename
- textDocument/foldingRange
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.