aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | CleanupKirill Bulatov2021-03-081-6/+0
| | | | |
| * | | | Restrict fuzzy qualifiers for nowKirill Bulatov2021-03-083-47/+26
| | | | |
| * | | | Test for fuzzy unresolved path maatchKirill Bulatov2021-03-081-0/+22
| | | | |
| * | | | Enforce the located imports' orderKirill Bulatov2021-03-083-8/+7
| | | | |
| * | | | Fix the completion labels and testsKirill Bulatov2021-03-084-65/+116
| | | | |
| * | | | Work towards better import labelsKirill Bulatov2021-03-0813-239/+243
| | | | |
| * | | | Profile import_assets betterKirill Bulatov2021-03-081-0/+5
| | | | |
| * | | | Update the docsKirill Bulatov2021-03-081-0/+39
| | | | |
| * | | | SimplifyKirill Bulatov2021-03-082-38/+23
| | | | |
| * | | | Refactor the import locationKirill Bulatov2021-03-083-162/+126
| | | | |
| * | | | Do not propose already imported importsKirill Bulatov2021-03-084-27/+45
| | | | |
| * | | | Properly handle turbofishes in qualifiersKirill Bulatov2021-03-085-8/+14
| | | | |
| * | | | Fix some testsKirill Bulatov2021-03-084-49/+143
| | | | |
| * | | | Return more data about located importsKirill Bulatov2021-03-089-125/+172
| | | | |
| * | | | Draft the qualifier import resolutionKirill Bulatov2021-03-084-43/+224
| | | | |
| * | | | Filter out path items by the qualifierKirill Bulatov2021-03-081-24/+15
| | | | |
| * | | | SimplifyKirill Bulatov2021-03-081-64/+37
| | | | |
| * | | | Find the code to changeKirill Bulatov2021-03-081-55/+130
| | | | |
| * | | | Test and initial refactoringKirill Bulatov2021-03-084-125/+101
| | | | |
* | | | | Make code less surprisingAleksey Kladov2021-03-091-17/+21
| |/ / / |/| | | | | | | | | | | Theres no reason to have literal `\n\n` in the source code
* | | | Merge #7931bors[bot]2021-03-091-26/+14
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7931: Use `Type::new_with_resolver_inner` more r=jonas-schievink a=jonas-schievink bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | | Use `Type::new_with_resolver_inner` moreJonas Schievink2021-03-091-26/+14
| | | | |
* | | | | Merge #7927bors[bot]2021-03-091-3/+7
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7927: Add more documentation for rustc_private r=matklad a=jyn514 Co-authored-by: Joshua Nelson <[email protected]>
| * | | | Add more documentation for rustc_privateJoshua Nelson2021-03-081-3/+7
| |/ / /
* | | | Fix formatDuong Do Minh Chau2021-03-091-9/+2
| | | |
* | | | Add trailing commasDuong Do Minh Chau2021-03-091-2/+2
| | | |
* | | | Update the test to match the changeDuong Do Minh Chau2021-03-091-0/+4
| | | |
* | | | Add completion to turn x.err into Err(x)Duong Do Minh Chau2021-03-091-2/+19
| | | |
* | | | Merge #7898bors[bot]2021-03-081-6/+67
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7898: generate_function assist: infer return type r=JoshMcguigan a=JoshMcguigan This PR makes two changes to the generate function assist: 1. Attempt to infer an appropriate return type for the generated function 2. If a return type is inferred, and that return type is not unit, don't render the snippet ```rust fn main() { let x: u32 = foo$0(); // ^^^ trigger the assist to generate this function } // BEFORE fn foo() ${0:-> ()} { todo!() } // AFTER (only change 1) fn foo() ${0:-> u32} { todo!() } // AFTER (change 1 and 2, note the lack of snippet around the return type) fn foo() -> u32 { todo!() } ``` These changes are made as two commits, in case we want to omit change 2. I personally feel like it is a nice change, but I could understand there being some opposition. #### Pros of change 2 If we are able to infer a return type, and especially if that return type is not the unit type, the return type is almost as likely to be correct as the argument names/types. I think this becomes even more true as people learn how this feature works. #### Cons of change 2 We could never be as confident about the return type as we are about the function argument types, so it is more likely a user will want to change that. Plus it is a confusing UX to sometimes have the cursor highlight the return type after triggering this assist and sometimes not have that happen. #### Why omit unit type? The assumption is that if we infer the return type as unit, it is likely just because of the current structure of the code rather than that actually being the desired return type. However, this is obviously just a heuristic and will sometimes be wrong. But being wrong here just means falling back to the exact behavior that existed before this PR. Co-authored-by: Josh Mcguigan <[email protected]>
| * | | generate_function assist don't render snippet if ret type inferredJosh Mcguigan2021-03-081-26/+47
| | | |
| * | | generate_function assist infer return typeJosh Mcguigan2021-03-061-3/+43
| | | |
* | | | Use upstream cov-markLaurențiu Nicola2021-03-0899-513/+338
| | | |
* | | | Hygiene is an internal implementation detail of the compilerAleksey Kladov2021-03-083-6/+11
| | | |
* | | | Remove useless code_model indirectionAleksey Kladov2021-03-085-2132/+2120
| | | |
* | | | Cleanup the error messageAleksey Kladov2021-03-081-1/+1
| | | |
* | | | Make `code generation` just workAleksey Kladov2021-03-082-3/+6
| | | | | | | | | | | | | | | | | | | | Contributors don't need to learn about `cargo xtask codegen` if `cargo test` just does the right thing.
* | | | Use the same name in xtask and test utilsAleksey Kladov2021-03-084-12/+12
| | | |
* | | | Generalize file ensuring infrastructureAleksey Kladov2021-03-082-6/+38
| | | |
* | | | Don't punish every crate with serde-jsonAleksey Kladov2021-03-083-98/+96
| | | |
* | | | Merge #7891bors[bot]2021-03-083-52/+112
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7891: Improve handling of rustc_private r=matklad a=DJMcNab This PR changes how `rust-analyzer` handles `rustc_private`. In particular, packages now must opt-in to using `rustc_private` in `Cargo.toml`, by adding: ```toml [package.metadata.rust-analyzer] rustc_private=true ``` This means that depending on crates which also use `rustc_private` will be significantly improved, since their dependencies on the `rustc_private` crates will be resolved properly. A similar approach could be used in #6714 to allow annotating that your package uses the `test` crate, although I have not yet handled that in this PR. Additionally, we now only index the crates which are transitive dependencies of `rustc_driver` in the `rustcSource` directory. This should not cause any change in behaviour when using `rustcSource: "discover"`, as the source used then will only be a partial clone. However, if `rustcSource` pointing at a local checkout of rustc, this should significantly improve the memory usage and lower indexing time. This is because we avoids indexing all crates in `src/tools/`, which includes `rust-analyzer` itself. Furthermore, we also prefer named dependencies over dependencies from `rustcSource`. This ensures that feature resolution for crates which are depended on by both `rustc` and your crate uses the correct set for analysing your crate. See also [introductory zulip stream](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Fixed.20crate.20graphs.20and.20optional.20builtin.20crates/near/229086673) I have tested this in [priroda](https://github.com/oli-obk/priroda/), and it provides a significant improvement to the development experience (once I give `miri` the required data in `Cargo.toml`) Todo: - [ ] Documentation This is ready to review, and I will add documentation if this would be accepted (or if I get time to do so anyway) Co-authored-by: Daniel McNab <[email protected]>
| * | | | Document rustc_private in metadataDaniel McNab2021-03-081-1/+2
| | | | |
| * | | | Never run cargo check on the rustc sourceDaniel McNab2021-03-081-4/+1
| | | | |
| * | | | Only show directory nameDaniel McNab2021-03-081-1/+1
| | | | |
| * | | | Revert "Support disabling rustc build scripts"Daniel McNab2021-03-088-53/+12
| | | | | | | | | | | | | | | | | | | | This reverts commit ddce6bb282764692d53b719bff4c37e3512d4556.
| * | | | Support disabling rustc build scriptsDaniel McNab2021-03-088-12/+54
| | | | |
| * | | | Fix the commentDaniel McNab2021-03-071-4/+4
| | | | | | | | | | | | | | | | | | | | It's worse than I thought...
| * | | | Extract the large nested block into a functionDaniel McNab2021-03-071-72/+98
| | | | | | | | | | | | | | | | | | | | | | | | | Also add some more detailed comments Extract into function deleted the previous comments
| * | | | Require opt in to rustc_privateDaniel McNab2021-03-072-70/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This gives the advantage that A future extension would be to check for `feature(rustc_private)` instead
| * | | | Don't double analyse the same crateDaniel McNab2021-03-071-1/+6
| | | | |
| * | | | Update crate graph to only use subcrates of rustc_driverDaniel McNab2021-03-071-38/+38
| | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 12:08:36 +0000