aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | Merge #1543bors[bot]2019-07-182-2/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | 1543: use more correct phantom types for ptrs r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | use more correct phantom types for ptrsAleksey Kladov2019-07-182-2/+2
|/ /
* | Merge #1538bors[bot]2019-07-173-15/+49
|\ \ | | | | | | | | | | | | | | | | | | | | | 1538: jemallocator 0.3 r=matklad a=kjeremy Co-authored-by: Jeremy A. Kolb <[email protected]>
| * | jemallocator 0.3Jeremy A. Kolb2019-07-173-15/+49
|/ /
* | Merge #1536bors[bot]2019-07-161-1/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1536: Add "Run" lens for binary runnables r=matklad a=SomeoneToIgnore Add an easy way to launch the different `main` methods from VS Code: Before: ![image](https://user-images.githubusercontent.com/2690773/61294531-b0111a80-a7de-11e9-856a-eedce52f883f.png) After: ![image](https://user-images.githubusercontent.com/2690773/61294556-bef7cd00-a7de-11e9-9fbd-cb5076e0b1b6.png) I've decided to omit the ️`▶️` symbol (as done for benches) since it looks a bit weird to me, but here's the version with it, just to compare: ![image](https://user-images.githubusercontent.com/2690773/61294597-dafb6e80-a7de-11e9-8f08-b513b8902ef5.png) Co-authored-by: Kirill Bulatov <[email protected]>
| * Add "Run" lens for binary runnablesKirill Bulatov2019-07-161-1/+1
|/
* Merge #1535bors[bot]2019-07-151-1/+1
|\ | | | | | | | | | | | | | | 1535: fix: spelling r=matklad a=martingronlund Co-authored-by: Martin Grönlund <[email protected]>
| * fix: spellingMartin Grönlund2019-07-151-1/+1
|/
* Merge #1534bors[bot]2019-07-153-46/+45
|\ | | | | | | | | | | | | | | 1534: cargo update r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * cargo updatekjeremy2019-07-153-46/+45
|/
* Merge #1532bors[bot]2019-07-1511-226/+198
|\ | | | | | | | | | | | | | | | | 1532: Some refactorings & update Chalk r=flodiebold a=flodiebold This does some of the renamings proposed in #1515, refactors `InferenceContext` a bit, and does a Cargo update, including fixing the build since I broke it by already pushing an updated branch to my Chalk fork :disappointed: We could also consider switching back to Chalk master; I couldn't reproduce any hangs with the floundering even on the rustc repo... Co-authored-by: Florian Diebold <[email protected]>
| * Switch to Chalk master, without fuelFlorian Diebold2019-07-153-27/+27
| |
| * Remove blacklist, instead mark `Sized` as non-enumerableFlorian Diebold2019-07-151-17/+3
| | | | | | | | | | This seems to be enough to prevent hanging in rust-analyzer, Chalk and the rustc repo.
| * Cargo update, including updating ChalkFlorian Diebold2019-07-142-127/+127
| |
| * Have InferenceContext contain an InferenceResult instead of duplicating all ↵Florian Diebold2019-07-141-36/+19
| | | | | | | | fields
| * Some renamings for clarityFlorian Diebold2019-07-149-25/+28
|/
* Merge #1528bors[bot]2019-07-142-11/+534
|\ | | | | | | | | | | | | | | 1528: More resolution modules with attribute path r=matklad a=andreevlex #1211 Co-authored-by: Alexander Andreev <[email protected]>
| * Fixed request commentsAlexander Andreev2019-07-142-66/+72
| |
| * Fixed commentsAlexander Andreev2019-07-131-2/+2
| |
| * More resolution modules with attribute pathAlexander Andreev2019-07-132-4/+521
|/ | | | #1211
* Merge #1525bors[bot]2019-07-125-16/+116
|\ | | | | | | | | | | | | | | 1525: Complete fields in enum variants r=matklad a=viorina Co-authored-by: Ekaterina Babshukova <[email protected]>
| * complete fields in enum variantsEkaterina Babshukova2019-07-125-16/+116
|/
* Merge #1524bors[bot]2019-07-1231-99/+109
|\ | | | | | | | | | | | | | | 1524: make Parse fields private r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * make Parse fields privateAleksey Kladov2019-07-1231-99/+109
|/ | | | this is in preparation for the new rowan API
* Merge #1523bors[bot]2019-07-122-0/+11
|\ | | | | | | | | | | | | | | 1523: account for dependencies when showing memory usage r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * account for dependencies when showing memory usageAleksey Kladov2019-07-122-0/+11
| |
* | Merge #1522bors[bot]2019-07-121-3/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1522: Bump lodash from 4.17.11 to 4.17.14 in /editors/code r=matklad a=dependabot[bot] Bumps [lodash](https://github.com/lodash/lodash) from 4.17.11 to 4.17.14. <details> <summary>Commits</summary> - [`be87d30`](https://github.com/lodash/lodash/commit/be87d303941222b97c482755afc0f4a77ce46c30) Bump to v4.17.14. - [`a6fe6b1`](https://github.com/lodash/lodash/commit/a6fe6b1e174fd02b5e60eb2664405f4c1262c300) Rebuild lodash and docs. - [`e371828`](https://github.com/lodash/lodash/commit/e37182845f16715a0d1c391c8662d83c55609cee) Bump to v4.17.13. - [`357e899`](https://github.com/lodash/lodash/commit/357e899e685872b4af5403ecc4b2a928f961ae63) Rebuild lodash and docs. - [`fd9a062`](https://github.com/lodash/lodash/commit/fd9a062d57646450b61f74029315abd4cc834b08) Bump to v4.17.12. - [`e77d681`](https://github.com/lodash/lodash/commit/e77d68121ff00ba86b53eed5893d35adfe94c9dd) Rebuild lodash and docs. - [`629d186`](https://github.com/lodash/lodash/commit/629d1865793182cd967196716f4beff223aa4a91) Update OpenJS references. - [`2406eac`](https://github.com/lodash/lodash/commit/2406eac542b2a1282be8d812a6d8a45433ade80a) Fix minified build. - [`17a34bc`](https://github.com/lodash/lodash/commit/17a34bc5854bb982ef333bfe7ae469f4dfcee0ec) Fix test bootstrap for core build. - [`53838a3`](https://github.com/lodash/lodash/commit/53838a38f8e4f6204ef2f837fecc4e07d09afe77) Fix tests in older browsers. - Additional commits viewable in [compare view](https://github.com/lodash/lodash/compare/4.17.11...4.17.14) </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=lodash&package-manager=npm_and_yarn&previous-version=4.17.11&new-version=4.17.14)](https://help.github.com/articles/configuring-automated-security-fixes) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language </details> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
| * | Bump lodash from 4.17.11 to 4.17.14 in /editors/codedependabot[bot]2019-07-121-3/+3
|/ / | | | | | | | | | | | | Bumps [lodash](https://github.com/lodash/lodash) from 4.17.11 to 4.17.14. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.11...4.17.14) Signed-off-by: dependabot[bot] <[email protected]>
* | Merge #1520bors[bot]2019-07-114-12/+15
|\ \ | |/ |/| | | | | | | | | | | | | | | 1520: Ignore workspace/didChangeConfiguration notifications. r=matklad a=bolinfest If the client happens to send a `workspace/didChangeConfiguration` notification, it is nicer if rust-analyzer can just ignore it rather than crash with an "unhandled notification" error. Co-authored-by: Michael Bolin <[email protected]>
| * Remove executeCommandProvider: apply_code_action.Michael Bolin2019-07-113-12/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This appears to have been introduced ages ago in https://github.com/rust-analyzer/rust-analyzer/commit/be742a587704f27f4e503c50f549aa9ec1527fcc but has since been removed. As it stands, it is problematic if multiple instances of the rust-analyzer LSP are launched during the same VS Code session because VS Code complains about multiple LSP servers trying to register the same command. Most LSP servers workaround this by parameterizing the command by the process id. For example, this is where `rls` does this: https://github.com/rust-lang/rls/blob/ff0b9057c8f62bc4f8113d741e96c9587ef1a817/rls/src/server/mod.rs#L413-L421 Though `apply_code_action` does not seems to be used, so it seems better to delete it than to parameterize it.
| * Ignore workspace/didChangeConfiguration notifications.Michael Bolin2019-07-112-4/+11
| |
* | Merge #1519bors[bot]2019-07-102-19/+17
|\ \ | | | | | | | | | | | | | | | | | | | | | 1519: Move whitespace manipulation inside AstEditor r=matklad a=viorina Co-authored-by: Ekaterina Babshukova <[email protected]>
| * | move whitespace manipulation inside AstEditorEkaterina Babshukova2019-07-102-19/+17
|/ /
* | Merge #1518bors[bot]2019-07-101-3/+5
|\ \ | |/ |/| | | | | | | | | | | 1518: Remove a fixme r=matklad a=killercup Just saw the new release of SmolStr and was reminded of this FIXME I added :) Co-authored-by: Pascal Hertleif <[email protected]>
| * Make clippy a bit happierPascal Hertleif2019-07-101-0/+4
| | | | | | | | | | Random drive-by fix. I honestly blame rust-analyzer itself on this, because I set its watch mode to use `cargo clippy` :shrug:
| * Resolve a FIXMEPascal Hertleif2019-07-101-3/+1
|/ | | | Now that we are using a newer smol_str release this can be simplified :)
* fix profile nameAleksey Kladov2019-07-091-1/+1
|
* Merge #1515bors[bot]2019-07-0911-119/+286
|\ | | | | | | | | | | | | | | | | | | | | | | 1515: Trait environment r=matklad a=flodiebold This adds the environment, i.e. the set of `where` clauses in scope, when solving trait goals. That means that e.g. in ```rust fn foo<T: SomeTrait>(t: T) {} ``` , we are able to complete methods of `SomeTrait` on the `t`. This affects the trait APIs quite a bit (since every method that needs to be able to solve for some trait needs to get this environment somehow), so I thought I'd do it rather sooner than later ;) Co-authored-by: Florian Diebold <[email protected]>
| * Unify `normalize` and `implements` to simplify codeFlorian Diebold2019-07-089-107/+67
| |
| * Use environment for associated type normalization as wellFlorian Diebold2019-07-087-20/+52
| |
| * Start handling environment in trait resolutionFlorian Diebold2019-07-086-14/+103
| | | | | | | | | | I.e. if we are inside a function with some where clauses, we assume these where clauses hold.
| * Refactor a bit & introduce Environment structFlorian Diebold2019-07-087-21/+107
| |
* | Merge #1512bors[bot]2019-07-093-17/+106
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 1512: Infer ? operator r=unrealhoang a=unrealhoang Logical continuation of https://github.com/rust-analyzer/rust-analyzer/pull/1501 cc https://github.com/rust-analyzer/rust-analyzer/issues/1426 Co-authored-by: Unreal Hoang <[email protected]>
| * | beautify testsUnreal Hoang2019-07-091-20/+36
| | |
| * | use namespaced consts for KnownNameUnreal Hoang2019-07-081-12/+10
| | |
| * | projection over std::ops::Try::Ok to infer try/?Unreal Hoang2019-07-083-2/+77
| | |
* | | Merge #1514bors[bot]2019-07-081-4/+6
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | 1514: Better completions for floating point primitive types r=flodiebold a=marcogroppo After #1499 completions for (some of) the inherent methods of `f32` and `f64` are now working. Unfortunately during method resolution we were only looking for the `f32` and `f64` language items defined in `libcore` and we were ignoring the methods defined in `libstd`. This PR fixes this issue. Co-authored-by: Marco Groppo <[email protected]>
| * | Look for the fXX_runtime lang items during method resolution.Marco Groppo2019-07-081-4/+6
|/ /
* | Merge #1513bors[bot]2019-07-089-36/+0
|\ \ | |/ |/| | | | | | | | | | | 1513: Remove unused dependencies r=matklad a=sinkuu Co-authored-by: Shotaro Yamada <[email protected]>
| * Remove unused dependenciesShotaro Yamada2019-07-089-36/+0
|/
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 01:02:11 +0000