aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | Use track caller in test documentationAleksey Kladov2021-02-101-1/+1
| | |/ / | |/| |
* | | | Merge #7619bors[bot]2021-02-101-0/+4
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7619: Add #[track_caller] to assist tests r=matklad a=yoshuawuyts This points the source of a failed assertion to the code which called it, rather than the location within the assertion helper method. While working on https://github.com/rust-analyzer/rust-analyzer/pull/7617 I had trouble locating some failing tests, and it was only by adding these attributes during development that I was able to locate them. This is only applied to test helpers, which means it comes at no runtime cost. And even then: I didn't experience any noticeable performance with this enabled or disabled. Mostly just a more pleasant experience debugging test failures (: Co-authored-by: Yoshua Wuyts <[email protected]>
| * | | Add #[track_caller] to assist testsYoshua Wuyts2021-02-091-0/+4
|/ / /
* | | Merge #7618bors[bot]2021-02-094-45/+95
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7618: Show qualified variant pattern completions r=Veykril a=Veykril ![UTMZyplssw](https://user-images.githubusercontent.com/3757771/107425157-e9c31800-6b1e-11eb-8963-96653115f8e0.gif) bors r+ Co-authored-by: Lukas Wirth <[email protected]>
| * | | Show qualified variant pattern completionsLukas Wirth2021-02-094-45/+95
|/ / /
* | | Merge #7616bors[bot]2021-02-093-6/+74
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7616: Show `Self` pattern and Self-prefixed enum-variant completions r=Veykril a=Veykril ![jDfQXNE0qZ](https://user-images.githubusercontent.com/3757771/107413514-1ff99b00-6b11-11eb-88b3-126cd106b514.gif) ![JpogVIgloq](https://user-images.githubusercontent.com/3757771/107413519-212ac800-6b11-11eb-8282-51115468dccc.gif) Variant pattern completions are to be done still. Closes #6549, at least that should address all that's left from that issue from what I can see. Co-authored-by: Lukas Wirth <[email protected]>
| * | | Show Self pattern completions for Adts if inside implsLukas Wirth2021-02-093-6/+40
| | | |
| * | | Show completions for enum variant with self prefix if inside implLukas Wirth2021-02-091-1/+35
| | | |
* | | | Merge #7615bors[bot]2021-02-094-8/+8628
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7615: Add parsing benchmark r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Add parsing benchmarkAleksey Kladov2021-02-094-8/+8628
| | | | |
* | | | | Merge #7614bors[bot]2021-02-097-237/+333
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7614: Unleash inner item resolution to users r=jonas-schievink a=jonas-schievink ![Peek 2021-02-09 17-30](https://user-images.githubusercontent.com/1786438/107394800-8627f300-6afc-11eb-8662-ed07226bc58f.gif) Co-authored-by: Jonas Schievink <[email protected]>
| * | | | | Remove unneeded returnJonas Schievink2021-02-091-2/+2
| | | | | |
| * | | | | Remove `pub`Jonas Schievink2021-02-091-2/+2
| | | | | |
| * | | | | Use `block_def_map` in `Resolver`Jonas Schievink2021-02-091-118/+97
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This required a few changes to not bail out immediately if a `ModuleScope` doesn't resolve a path. The `LocalItemsScope` hack is now removed.
| * | | | | Teach `find_path` about inner itemsJonas Schievink2021-02-091-10/+91
| | | | | |
| * | | | | Add another block def map testJonas Schievink2021-02-091-0/+27
| | | | | |
| * | | | | Make `with_ancestor_maps` publicJonas Schievink2021-02-091-1/+1
| | | | | |
| * | | | | Add `TestDB::module_at_position`Jonas Schievink2021-02-092-104/+99
| | | | | |
| * | | | | Add expression scopes for blocksJonas Schievink2021-02-091-4/+18
| | |/ / / | |/| | |
* | | | | Merge #7613bors[bot]2021-02-098-4001/+102
|\ \ \ \ \ | |/ / / / |/| / / / | |/ / / | | | | | | | | | | | | | | | | 7613: Benchmarking infrastructure r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Infra for "unit" benchmarkingAleksey Kladov2021-02-098-4001/+102
| | | |
* | | | Merge #7611bors[bot]2021-02-094-49/+63
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7611: Cleanups r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | restore accidentally deleted testAleksey Kladov2021-02-091-0/+13
| | | |
| * | | More precise navigation to parentAleksey Kladov2021-02-093-10/+13
| | | |
| * | | Cleanup testsAleksey Kladov2021-02-093-55/+53
| | | |
* | | | Merge #7597bors[bot]2021-02-091-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7597: Set remote branch on xtask promote r=matklad a=lnicola to hopefully fix this: ``` $ git switch master Already on 'master' Your branch is up to date with 'upstream/master'. $ git fetch upstream $ git reset --hard upstream/master HEAD is now at 921ec4b3fca Auto merge of #81313 - LeSeulArtichaut:revert-32558, r=jyn514 $ git submodule update --recursive Submodule path 'src/tools/rust-analyzer': checked out '1a59f75cdaa730c16a694a4294eccf6dfe6fe0ad' $ git switch -c rust-analyzer-2021-02-08 Switched to a new branch 'rust-analyzer-2021-02-08' $ git fetch origin $ git reset --hard origin/release HEAD is now at 336909b63 Merge #7587 $ git add src/tools/rust-analyzer $ git commit "-m:arrow_up: rust-analyzer" [rust-analyzer-2021-02-08 1774ec1a683] :arrow_up: rust-analyzer 1 file changed, 1 insertion(+), 1 deletion(-) $ git push fatal: The current branch rust-analyzer-2021-02-08 has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin rust-analyzer-2021-02-08 Error: command `git push` failed, exit code: 128 ``` Co-authored-by: LaurenÈ›iu Nicola <[email protected]>
| * | | | Track remote branch on xtask promoteLaurențiu Nicola2021-02-091-1/+1
| | |/ / | |/| |
* | | | Merge #7610bors[bot]2021-02-093-217/+234
|\ \ \ \ | | |/ / | |/| / | |_|/ |/| | | | | | | | | | | | | | 7610: Cleanup test r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Cleanup testAleksey Kladov2021-02-091-20/+21
| | |
| * | Fix highlighting of injected attributesAleksey Kladov2021-02-091-0/+44
| | |
| * | Modernize testsAleksey Kladov2021-02-091-197/+169
|/ /
* | Merge #7602bors[bot]2021-02-082-11/+38
|\ \ | | | | | | | | | | | | | | | | | | | | | 7602: Check for dyn impls in method resolution r=flodiebold a=Veykril Fixes #6777 Co-authored-by: Lukas Wirth <[email protected]>
| * | Check for dyn impls in method resolutionLukas Wirth2021-02-082-11/+38
| | |
* | | Merge #7600bors[bot]2021-02-084-22/+23
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7600: Update crates r=flodiebold a=kjeremy Pulls in https://github.com/rust-lang/chalk/pull/682 Co-authored-by: kjeremy <[email protected]>
| * | | Update crateskjeremy2021-02-084-22/+23
| | | | | | | | | | | | | | | | Pulls in https://github.com/rust-lang/chalk/pull/682
* | | | Merge #7599bors[bot]2021-02-081-0/+2
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 7599: Add emacs guide r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Add emacs guideAleksey Kladov2021-02-081-0/+2
|/ / /
* | | Merge #7595bors[bot]2021-02-085-20/+70
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7595: Add `config: &CargoConfig` parameter to `fn load_cargo(…)` r=matklad a=regexident For projects using rust-analyzer as a library it is desirable to be able to provide a custom-config to `fn load_cargo(…)` to pass features, etc, rather than having to copy & paste `fn load_cargo(…)` into one's project and maintain a fork of it and keep it in sync with upstream. Co-authored-by: Vincent Esche <[email protected]>
| * | | Consolidate `fn load_cargo(…)` parameters into `struct LoadCargoConfig ↵Vincent Esche2021-02-085-31/+70
| | | | | | | | | | | | | | | | { … }`
| * | | Add `config: &CargoConfig` parameter to `fn load_cargo(…)`Vincent Esche2021-02-085-7/+18
|/ / /
* | | Merge #7592bors[bot]2021-02-081-0/+10
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7592: [Doc] Note about Eclipse IDE support r=lnicola a=mickaelistria Co-authored-by: Mickael Istria <[email protected]>
| * | | [Doc] Note about Eclipse IDE supportMickael Istria2021-02-081-0/+10
| | |/ | |/|
* | | Merge #7593bors[bot]2021-02-081-0/+8
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7593: fix: add for keyword in completion #7588 r=lnicola a=gowrizrh Fixes #7588 bors r+ Co-authored-by: Gowri <[email protected]> Co-authored-by: Gowri <[email protected]>
| * | | chore: swap order of placeholdersGowri2021-02-081-1/+1
| | | |
| * | | ci: update relevant test case expected valuesGowri2021-02-071-0/+7
| | | |
| * | | fix: add for keyword in completion #7588Gowri2021-02-071-0/+1
| |/ /
* | | Merge #7549bors[bot]2021-02-081-5/+73
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7549: Documentation: Explain how initial configuration is sent over LSP and document vim-lsp r=ilya-bobyr a=ilya-bobyr This request contains two related but independent changes. The first explains `rust-analyzer` initial configuration over LSP. The second - adds documentation on `vim-lsp` Vim plugin and provides an example of the initial configuration for `rust-analyzer` when using this particular LSP client. Let me know if you would prefer the changes to be reviewed in two separate pull requests. Co-authored-by: Ilya Bobyr <[email protected]>
| * | Vim docs: vim-lsp with initial configuration.Ilya Bobyr2021-02-081-0/+46
| | | | | | | | | | | | | | | | | | `vim-lsp` is another popular LSP client for Vim. And, as there is no `rust-analyzer` specific UI, it is non-trivial to figure out how the initial configuration is performed.
| * | Explain how initial configuration is sent over LSP.Ilya Bobyr2021-02-081-5/+27
|/ /
* | Merge #7587bors[bot]2021-02-079-40/+40
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 7587: AdtDef -> Adt r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 20:31:54 +0000