Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Happy path implemented | Kirill Bulatov | 2020-09-09 | 1 | -2/+2 |
| | |||||
* | Better API | Kirill Bulatov | 2020-09-09 | 1 | -0/+3 |
| | |||||
* | Support extern types | Jonas Schievink | 2020-08-24 | 2 | -0/+6 |
| | |||||
* | :arrow_up: ungrammar | Aleksey Kladov | 2020-08-21 | 1 | -1/+1 |
| | |||||
* | Switch to expect_test from crates.io | Aleksey Kladov | 2020-08-21 | 3 | -3/+3 |
| | |||||
* | Add type safety to diagnostic codes | Aleksey Kladov | 2020-08-18 | 1 | -3/+3 |
| | |||||
* | Merge #5682 | bors[bot] | 2020-08-18 | 1 | -0/+3 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | 5682: Add an option to disable diagnostics r=matklad a=popzxc As far as I know, currently it's not possible to disable a selected type of diagnostics provided by `rust-analyzer`. This causes an inconvenient situation with a false-positive warnings: you either have to disable all the diagnostics, or you have to ignore these warnings. There are some open issues related to this problem, e.g.: https://github.com/rust-analyzer/rust-analyzer/issues/5412, https://github.com/rust-analyzer/rust-analyzer/issues/5502 This PR attempts to make it possible to selectively disable some diagnostics on per-project basis. Co-authored-by: Igor Aleksanov <[email protected]> | ||||
| * | Merge branch 'master' into add-disable-diagnostics | Igor Aleksanov | 2020-08-14 | 1 | -0/+3 |
| | | |||||
* | | Remove deprecated Path::from_ast | Aleksey Kladov | 2020-08-15 | 1 | -6/+0 |
|/ | | | | Long term, we probably should make hir::Path private to hir. | ||||
* | Rename ra_hir_def -> hir_def | Aleksey Kladov | 2020-08-13 | 43 | -0/+15284 |