aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge #8714bors[bot]2021-05-042-23/+49
|\ | | | | | | | | | | | | | | | | 8714: internal: remove one more usage of the rewriter r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * internal: remove one more usage of the rewriterAleksey Kladov2021-05-042-23/+49
| |
* | Merge #8716bors[bot]2021-05-043-13/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8716: Replace `memmap` with `memmap2` in `proc_macro_api` r=edwin0cheng a=memoryruins #7522 did the same for `proc_macro_srv` before this usage of `memmap` was introduced to `proc_macro_api` in #6822 . Something like [`cargo-deny`](https://github.com/EmbarkStudios/cargo-deny-action) could help prevent specific crates (and versions, licenses, etc) from being introduced into the crate tree, but that's unrelated to this pull request. Co-authored-by: memoryruins <[email protected]>
| * | Replace `memmap` to `memmap2` in `proc_macro_api`memoryruins2021-05-043-13/+3
|/ /
* | Merge #8715bors[bot]2021-05-032-117/+113
|\ \ | |/ |/| | | | | | | | | | | 8715: Make CompletionContext expected_type smarter r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Tobias Wirth <[email protected]>
| * Make CompletionContext expected_type smarterLukas Tobias Wirth2021-05-032-117/+113
| |
* | Merge #8482bors[bot]2021-05-031-0/+35
|\ \ | | | | | | | | | | | | | | | | | | | | | 8482: Mention how to customize unsafe operation styles r=matklad a=danielzfranklin I was confused about how to do this, so I filed #8474. I apologize for initially filing this incorrectly and spamming people. Co-authored-by: Daniel Franklin <[email protected]>
| * | Merge with semantic style sectionDaniel Franklin2021-05-031-8/+25
| | |
| * | Mention how to customize unsafe operation stylesDaniel Franklin2021-04-121-0/+18
| | | | | | | | | | | | | | | I was confused about how to do this, so I filed [an issue][issue]. [issue]: rust-analyzer/rust-analyzer#8474
* | | Merge #8712bors[bot]2021-05-031-4/+36
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | 8712: Map nodes to their mutable counterpart before mutating in reorder_impl r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Tobias Wirth <[email protected]>
| * | Don't mutate the tree while traversing in reorder_implLukas Tobias Wirth2021-05-031-4/+36
|/ /
* | Merge #8710bors[bot]2021-05-031-0/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 8710: feat: build releases with lto=true r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | feat: build releases with lto=trueAleksey Kladov2021-05-031-0/+1
| | | | | | | | | | | | closes #8050
* | | Merge #8427bors[bot]2021-05-034-117/+4
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | 8427: Move CI to rust-cache Action r=matklad a=Swatinem This is humbling. I actually took inspiration from RAs pre-cache xtask when developing my action ;-) Closes #7731 Co-authored-by: Arpad Borsos <[email protected]>
| * | pin cache actionArpad Borsos2021-04-081-2/+2
| | |
| * | noop to test CI cacheArpad Borsos2021-04-080-0/+0
| | |
| * | Move CI to rust-cache ActionArpad Borsos2021-04-084-117/+4
| | |
* | | Merge #8709bors[bot]2021-05-021-36/+37
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8709: cargo update r=kjeremy a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * | | cargo updateJeremy Kolb2021-05-021-36/+37
|/ / /
* | | Merge #8708bors[bot]2021-05-022-20/+11
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8708: fix: don't duplicate Progerss::Finised for cache priming r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | fix: don't duplicate Progerss::Finised for cache primingAleksey Kladov2021-05-022-20/+11
|/ / /
* | | Merge #8693bors[bot]2021-05-022-0/+18
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8693: Ensure that only one cache priming task can run at a time r=matklad a=Bobo1239 Fixes #8632. Co-authored-by: Boris-Chengbiao Zhou <[email protected]>
| * | | Ensure that only one cache priming task can run at a timeBoris-Chengbiao Zhou2021-04-302-0/+18
| | | | | | | | | | | | | | | | Fixes #8632.
* | | | Merge #8701bors[bot]2021-05-011-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8701: Fix feature description inconsistency r=Veykril a=brandondong ![image](https://user-images.githubusercontent.com/13722457/116768676-4d0d6980-a9ed-11eb-8d7e-c7d340a99064.png) Just something that bugged me :) Co-authored-by: Brandon <[email protected]>
| * | | | Fix feature description inconsistencyBrandon2021-05-011-1/+1
|/ / / /
* | | | Merge #8698bors[bot]2021-04-301-2/+28
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8698: fix: search only crate-level prelude when looking for an item r=jonas-schievink a=jonas-schievink Fixes https://github.com/rust-analyzer/rust-analyzer/issues/8688 bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | | find_path: check only crate-level preludeJonas Schievink2021-04-301-2/+28
|/ / / /
* | | | Merge #8692bors[bot]2021-04-304-25/+100
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8692: Fix panic caused by new Try trait definition r=flodiebold a=flodiebold The new Try trait definition caused a query cycle for us. This adds recovery for that cycle, but also fixes the cause, which is that we went through the supertraits when resolving `<T as Trait>::Assoc`, which isn't actually necessary. I also rewrote `all_super_trait_refs` to an iterator before I realized what the actual problem was, so I kept that. Fixes #8686. Co-authored-by: Florian Diebold <[email protected]>
| * | | | Don't look in super traits for <T as Trait>::AssocFlorian Diebold2021-04-292-7/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This isn't actually how it works, you have to specify the exact trait that has the associated type. Fixes #8686.
| * | | | Rewrite all_super_trait_refs as an iteratorFlorian Diebold2021-04-291-18/+34
| | | | | | | | | | | | | | | | | | | | | | | | | Doesn't fix the bug I was trying to fix, but now that I did it anyway it seems fine to keep.
| * | | | Handle cycles in generic_defaults more gracefullyFlorian Diebold2021-04-292-0/+22
| | | | |
| * | | | Add test for #8686Florian Diebold2021-04-291-0/+30
| |/ / /
* | | | Merge #8695bors[bot]2021-04-308-12/+12
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 8695: internal: fix naming polarity r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | internal: fix naming polarityAleksey Kladov2021-04-304-6/+6
| | | | | | | | | | | | | | | | | | | | Type Constructors have *parameters*, when they are substituted with type *arguments*, we have a type.
| * | | internal: normalize nameAleksey Kladov2021-04-305-6/+6
| | | | | | | | | | | | | | | | All def types in hir are unsubstituted
* | | | Merge #8687bors[bot]2021-04-292-0/+40
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8687: fix: closure unify without check ClosureId r=lnicola a=komonad Previously, the unification of closure types is blocked by `Ty.equals_ctor` which compares the ClosureId of the closures. Here is a workaround to allow closures to unify their substitutions. Fixes #8604. Co-authored-by: Comonad <[email protected]>
| * | | | fix: closure unify without check ClosureIdComonad2021-04-292-0/+40
|/ / / / | | | | | | | | | | | | closes #8604
* | | | Merge #8685bors[bot]2021-04-294-0/+141
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8685: feat: parse const param defaults r=jonas-schievink a=jonas-schievink These will probably be stabilized in a few releases, let's make sure we can at least parse them bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | | Parse const param defaultsJonas Schievink2021-04-294-0/+141
|/ / / /
* | | | Merge #8684bors[bot]2021-04-293-0/+40
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8684: Correctly parse negated literals as const args r=jonas-schievink a=jonas-schievink Previously we didn't accept `S::<-0>;` bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | Correctly parse negated literals as const argsJonas Schievink2021-04-293-0/+40
|/ / /
* | | Merge #8683bors[bot]2021-04-283-13/+11
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8683: internal: ensure that client and server-side configs are not mixed up r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | internal: ensure that client and server-side configs are not mixed upAleksey Kladov2021-04-283-13/+11
|/ / / | | | | | | | | | https://github.com/rust-lang/rust/issues/84647 would help big time here.
* | | Merge #8624bors[bot]2021-04-275-8/+60
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8624: Automatically detect rust library source file map r=vsrs a=vsrs This PR adds a new possible `rust-analyzer.debug.sourceFileMap` value: ```json { "rust-analyzer.debug.sourceFileMap": "auto" } ``` I did not make it the default because it uses two shell calls (`rustc --print sysroot` and `rustc -V -v`). First one can be slow (https://github.com/rust-lang/rustup/issues/783) Fixes #8619 Co-authored-by: vsrs <[email protected]>
| * | | Use explicit rustc commit-hashvsrs2021-04-223-3/+15
| | | | | | | | | | | | | | | | Required for lldb on mac
| * | | Add special `auto` value for `debug.sourceFileMap`vsrs2021-04-225-27/+38
| | | |
| * | | Autodetect rust library source file mapvsrs2021-04-222-2/+31
| | | |
| | | |
| \ \ \
*-. \ \ \ Merge #8629 #8657bors[bot]2021-04-272-404/+486
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8629: Allow pressing | to surround closure arguments in VSCode r=matklad a=Smittyvb This makes pressing <kbd>|</kbd> while some text is selected surround that text with pipes. This is useful when writing closures. In this demo, I press <kbd>|</kbd> to easily surround some text (`predicate`) with pipe characters to create a closure. Before, this would have replaced `predicate` with just `|`. ![](https://user-images.githubusercontent.com/10530973/115778847-3c257e00-a385-11eb-8c80-e0db970747db.gif) (I am getting failures when I do `cargo test` even on `master` locally (due to #8585 I think), but GH Actions is fine with this) 8657: npm update r=matklad a=kjeremy Co-authored-by: Smittyvb <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| | * | | | npm updateJeremy Kolb2021-04-251-407/+484
| | | | | |
| * | | | | Support | as a surrounding pairsSmittyvb2021-04-221-1/+2
| | | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-26 16:37:25 +0000