rust-analyzer

mirror of https://github.com/rust-lang/rust-analyzer synced 2025-01-13 21:54:42 +00:00

No description

Find a file

bors 64a140527b Auto merge of #17882 - ShoyuVanilla:issue-17866, r=lnicola fix: Panic while canonicalizing erroneous projection type Fixes #17866 The root cause of #17866 is quite horrifyng 😨 ```rust trait T { type A; } type Foo = <S as T>::A; // note that S isn't defined fn main() { Foo {} } ``` While inferencing alias type `Foo = <S as T>::A`; `78c2bdce86/crates/hir-ty/src/infer.rs (L1388-L1398)` the error type `S` in it is substituted by inference var in L1396 above as below; `78c2bdce86/crates/hir-ty/src/infer/unify.rs (L866-L869)` This new inference var's index is `1`, as the type inferecing procedure here previously inserted another inference var into same `InferenceTable`. But after that, the projection type made from the above then passed to the following function; `78c2bdce86/crates/hir-ty/src/traits.rs (L88-L96)` here, a whole new `InferenceTable` is made, without any inference var and in the L94, this table calls; `78c2bdce86/crates/hir-ty/src/infer/unify.rs (L364-L370)` And while registering `AliasEq` `obligation`, this obligation contains inference var `?1` made from the previous table, but this table has only one inference var `?0` made at L365. So, the chalk panics when we try to canonicalize that obligation to register it, because the obligation contains an inference var `?1` that the canonicalizing table doesn't have. Currently, we are calling `InferenceTable::new()` to do some normalizing, unifying or coercing things to some targets that might contain inference var that the new table doesn't have. I think that this is quite dangerous footgun because the inference var is just an index that does not contain the information which table does it made from, so sometimes this "foreign" index might cause panic like this case, or point at the wrong variable. This PR mitigates such behaviour simply by inserting sufficient number of inference vars to new table to avoid such problem. This strategy doesn't harm current r-a's intention because the inference vars that passed into new tables are just "unresolved" variables in current r-a, so this is just making sure that such "unresolved" variables exist in the new table		2024-08-14 15:12:03 +00:00
.cargo	fix: Fix generated markers not being patchable in package.json	2024-06-08 12:54:43 +02:00
.github	Only keep lib/ in publish-libs	2024-08-12 13:45:38 +03:00
.vscode	feat: use vscode log format for client logs	2024-07-27 21:43:35 -07:00
assets	Automatically change text color in logo based on dark mode	2022-03-06 23:06:53 +11:00
bench_data	Spelling	2023-04-19 09:45:55 -04:00
crates	Auto merge of #17882 - ShoyuVanilla:issue-17866, r=lnicola	2024-08-14 15:12:03 +00:00
docs	internal: Reply to requests with defaults when vfs is still loading	2024-08-12 12:05:15 +02:00
editors/code	Allow rust-project.json to be hidden	2024-08-07 03:27:03 +02:00
lib	Use crossbeam-channel from the workspace	2024-08-09 23:48:03 +02:00
xtask	Allow new license combination	2024-08-12 12:51:47 +02:00
.editorconfig	add max_line_length to .editorconfig	2024-01-20 17:14:00 +03:00
.git-blame-ignore-revs	Show workspace info in the status bar	2024-04-26 11:28:33 +02:00
.gitattributes	Fix .gitattributes for test_data	2022-07-24 14:05:35 +02:00
.gitignore	internal: add "Shuffle Crate Graph" command	2021-12-07 16:37:19 +01:00
.typos.toml	Implement rough symbol interning infra	2024-07-12 16:01:47 +02:00
Cargo.lock	Bump `rustc_pattern_analysis`	2024-08-13 23:15:37 +09:00
Cargo.toml	Bump `rustc_pattern_analysis`	2024-08-13 23:15:37 +09:00
clippy.toml	Lint debug prints and disallowed types with clippy	2024-02-01 17:57:27 +01:00
CONTRIBUTING.md	Add CONTRIBUTING.md	2024-04-18 10:24:40 +02:00
LICENSE-APACHE	Licenses	2018-01-10 22:47:04 +03:00
LICENSE-MIT	Licenses	2018-01-10 22:47:04 +03:00
PRIVACY.md	Update privacy note	2021-12-23 14:04:15 +02:00
README.md	Add CONTRIBUTING.md	2024-04-18 10:24:40 +02:00
rust-bors.toml	Prepare for rust-bors	2023-10-05 15:26:09 +03:00
rust-version	Preparing for merge from rust-lang/rust	2024-08-13 17:56:37 +03:00
rustfmt.toml	Shuffle hir-expand things around	2024-01-26 19:28:39 +01:00
triagebot.toml	Update triagebot.toml	2024-06-27 10:32:13 +02:00

README.md

rust-analyzer is a 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.

Quick Start

https://rust-analyzer.github.io/manual.html#installation

Documentation

If you want to contribute to rust-analyzer check out the CONTRIBUTING.md or if you are just curious about how things work under the hood, check the ./docs/dev folder.

If you want to use rust-analyzer's language server with your editor of choice, check the manual folder. It also contains some tips & tricks to help you be more productive when using rust-analyzer.

Security and Privacy

See the corresponding sections of the manual.

Communication

For usage and troubleshooting requests, please use "IDEs and Editors" category of the Rust forum:

https://users.rust-lang.org/c/ide/14

For questions about development and implementation, join rust-analyzer working group on Zulip:

https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer

Quick Links

Website: https://rust-analyzer.github.io/
Metrics: https://rust-analyzer.github.io/metrics/
API docs: https://rust-lang.github.io/rust-analyzer/ide/
Changelog: https://rust-analyzer.github.io/thisweek

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.