aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | 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
| | | | | |
* | | | | | Merge #8679bors[bot]2021-04-271-0/+6
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8679: fix: don't show error message for a valid notification r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | | fix: don't show error message for a valid notificationAleksey Kladov2021-04-271-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #6782, #6772
* | | | | | | Merge #8677bors[bot]2021-04-272-3/+3
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8677: Return ServerNotInitialized according to the spec r=kjeremy a=kjeremy According to the spec we should return ServerNotInitialized if the server is waiting for an initialize request and something else comes in. Upgrading to lsp-server 0.5.1 will do this and retry until the initialize request comes in. Fixes #8581 Co-authored-by: Jeremy Kolb <[email protected]>
| * | | | | | | Return ServerNotInitialized according to the specJeremy Kolb2021-04-272-3/+3
|/ / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | According to the spec we should return ServerNotInitialized if the server is waiting for an initialize request and something else comes in. Upgrading to lsp-server 0.5.1 will do this and retry until the initialize request comes in. Fixes #8581
* | | | | | | Merge #8617bors[bot]2021-04-276-10/+59
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8617: Add option to opt out of smaller font size for inlay hints. r=SomeoneToIgnore a=jmederosalvarado As requested on issue #6883 this PR provides an option for users to opt out of the smaller font size for inlay hints. Part of #6883. Co-authored-by: Jorge Mederos Alvarado <[email protected]>
| * | | | | | | Fix how and when old inlay hint decorations are disposedJorge Mederos Alvarado2021-04-271-16/+33
| | | | | | | |
| * | | | | | | Add config optionsJorge Mederos Alvarado2021-04-272-0/+7
| | | | | | | |
| * | | | | | | Add option to opt out from smaller inlay hints font sizeJorge Mederos Alvarado2021-04-272-6/+30
| | | | | | | |
| * | | | | | | add option to package.jsonJorge Mederos Alvarado2021-04-272-4/+5
|/ / / / / / /
* | | | | | | Merge #8671bors[bot]2021-04-261-12/+3
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8671: minor: simplify r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | | | minor: simplifyAleksey Kladov2021-04-261-12/+3
| | | | | | | |
* | | | | | | | Merge #8670bors[bot]2021-04-261-1/+1
|\| | | | | | | | |/ / / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8670: fix: make error message in the status bar more useful r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | | fix: make error message in the status bar more usefulAleksey Kladov2021-04-261-1/+1
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At the moment,the popup is just a bazillion of Cargo's "Compiling this\nCompiling that", which is not that useful. --quiet still displays error, which is what we needc
* | | | | | Merge #8668bors[bot]2021-04-263-3/+3
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8668: Use more cross-platform utc `date` argument r=matklad a=SomeoneToIgnore Part of https://github.com/rust-analyzer/rust-analyzer/issues/8571 ``` $ docker run -it --rm ubuntu:20.04 bash root@7393d1e7bbad:/# date -u +%Y-%m-%d 2021-04-26 ``` ``` $ date -u +%Y-%m-%d 2021-04-26 $ uname -a Darwin alaptop.local 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 ``` Some of the places where I've change this do not really require it (since macos bin would have failed with `--iso` param also), but I've changed them for consistency. Co-authored-by: Kirill Bulatov <[email protected]>
| * | | | | | Use -u instead of --utc date flagKirill Bulatov2021-04-263-3/+3
|/ / / / / /
* | | | | | Merge #8666bors[bot]2021-04-265-30/+20
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8666: fix: correct version string on windows and mac r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | | fix: add date to the version string on MacAleksey Kladov2021-04-262-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It doesn't support `--iso`
| * | | | | | fix: dont' misundentify nightly as stable in --version on Mac&WinAleksey Kladov2021-04-264-28/+18
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | We used to set `--nightly` in CI, and only for linux. Let's detect this in xtask instead.
* | | | | | Merge #8661bors[bot]2021-04-261-1/+10
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8661: internal: make normal release after a poin release less annoying r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | | Update xtask/src/release.rsAleksey Kladov2021-04-261-1/+1
| | | | | | | | | | | | | | | | | | | | | Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | | | | Update xtask/src/release.rsAleksey Kladov2021-04-261-1/+1
| | | | | | | | | | | | | | | | | | | | | Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | | | | internal: make normal release after a poin release less annoyingAleksey Kladov2021-04-261-1/+10
|/ / / / / /
* | | | | | Merge #8660bors[bot]2021-04-262-4/+9
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8660: Added `mutable` semantic token modifier for `&mut self` methods r=Veykril a=1c3t3a This closes #8644. Co-authored-by: Bastian Kersting <[email protected]>
| * | | | | | Fixed formattingBastian Kersting2021-04-261-1/+1
| | | | | | |
| * | | | | | Added mutable semantic token modifier for &mut self methodsBastian Kersting2021-04-262-4/+9
|/ / / / / /
* | | | | | Merge #8658bors[bot]2021-04-252-6/+105
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8658: Check more carefully for cases where a rename can't be done r=Veykril a=dzhu Attempting to rename an element of a tuple field would previously replace the type with the new name, which doesn't make sense; now it fails instead. The check is done in both `prepare_rename` and `rename` so that the case is caught before the user is prompted for a new name. Some other existing failure cases are also now additionally checked in `prepare_rename`. Closes: #8592 (I threw in some doc edits for a relevant type; of course, I can remove those if the policy here is to be strict about scope of changes within a PR.) Co-authored-by: Danny Zhu <[email protected]>
| * | | | | | Check more carefully for cases where a rename can't be doneDanny Zhu2021-04-252-6/+105
| | |/ / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Attempting to rename an element of a tuple field would previously replace the type with the new name, which doesn't make sense; now it fails instead. The check is done in both `prepare_rename` and `rename` so that the case is caught before the user is prompted for a new name. Some other existing failure cases are also now additionally checked in `prepare_rename`.
* | | | | | Merge #8656bors[bot]2021-04-251-4/+4
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8656: Update deps r=kjeremy a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * | | | | Update depsJeremy Kolb2021-04-251-4/+4
|/ / / / /
* | | | | Merge #8647bors[bot]2021-04-248-329/+344
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8647: internal: Split out merge_imports module from helpers::insert_use r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Wirth <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 20:58:04 +0000