aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | | Add more tests, refactor array lengths/consteval workJade2021-05-148-35/+223
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix #2922: add unknown length as a condition for a type having unknown. Incorporate reviews: * Extract some of the const evaluation workings into functions * Add fixmes on the hacks * Add tests for impls on specific array lengths (these work!!! 😁) * Add tests for const generics (indeed we don't support it yet)
| * | | | | Test lowering byte strings some moreJade2021-05-131-14/+25
| | | | | |
| * | | | | Add support for lengths in array repeats, if they are literalsJade2021-05-134-11/+22
| | | | | | | | | | | | | | | | | | | | | | | | Now we will get the type of `[0u8; 4]`.
| * | | | | Support length for ByteStringsJade2021-05-138-33/+85
| | | | | | | | | | | | | | | | | | | | | | | | I am not confident that my added byte string parsing is right.
| * | | | | Add lowering of array lengths in typesJade2021-05-1310-79/+114
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now e.g. ```rust fn a(b: [u8; 2]) { } ``` will know about the length of b.
* | | | | Merge #8848bors[bot]2021-05-156-16/+38
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8848: Attach comments to ast::Impl r=Veykril a=Veykril bors r+ Fixes #8847 Co-authored-by: Lukas Wirth <[email protected]>
| * | | | Attach comments to ast::ImplLukas Wirth2021-05-154-6/+30
| | | | |
| * | | | simplifyLukas Wirth2021-05-152-10/+8
| | |/ / | |/| |
* / | | simplifyLukas Wirth2021-05-151-12/+10
|/ / /
* | | Merge #8840bors[bot]2021-05-143-5/+7
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8840: fix: false positive "Missing match arm" when a tuple pattern is shorter than scrutinee type. r=Veykril a=iDawer ![Screenshot_20210515_003035](https://user-images.githubusercontent.com/7803845/118320023-2bcb7380-b4eb-11eb-9de6-d8762f981dc2.jpg) Match checking diagnostic shouldn't fire when there is type mismatches. rust-analyzer fd109fb58 2021-05-10 dev (This is part of the preparation for https://github.com/rust-analyzer/rust-analyzer/pull/8717) Co-authored-by: Dawer <[email protected]>
| * | | Fix false positive "Missing match arm".Dawer2021-05-143-5/+7
| | | |
* | | | Merge #8839bors[bot]2021-05-141-2/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8839: minor: more useful bench r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | minor: more useful benchAleksey Kladov2021-05-141-2/+2
| |/ / /
* | | | Merge #8819bors[bot]2021-05-142-0/+2
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8819: Use package root as `cargo check` working directory r=matklad a=bcully Cargo commands are affected by the `.cargo/config` files above their working directory. If cargo is invoked from above the directory holding `Cargo.toml`, it may not pick up important settings like registry replacements, causing it to behave differently or even fail. Most cargo invocations are currently setting their working directories to the directory containing `Cargo.toml`, but a couple of paths remain in which cargo is invoked from the default workspace root instead. This change fixes that, resolving some cargo check failures that I experienced in a multi-root workspace in which packages used different registries. Co-authored-by: Brendan Cully <[email protected]>
| * | | Use package root as `cargo check` working directoryBrendan Cully2021-05-132-0/+2
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cargo commands are affected by the `.cargo/config` files above their working directory. If cargo is invoked from above the directory holding `Cargo.toml`, it may not pick up important settings like registry replacements, causing it to behave differently or even fail. Most cargo invocations are currently setting their working directories to the directory containing `Cargo.toml`, but a couple of paths remain in which cargo is invoked from the default workspace root instead. This change fixes that, resolving some cargo check failures that I experienced in a multi-root workspace in which packages used different registries.
* | | internal: use more mutable APIsAleksey Kladov2021-05-143-53/+33
| | |
* | | internal: use standard style for testsAleksey Kladov2021-05-141-54/+99
| | |
* | | internal: rewrite assoc item manipulaion to use mutable treesAleksey Kladov2021-05-146-167/+88
| | |
* | | internal: remove SyntaxRewriterAleksey Kladov2021-05-143-154/+7
| | |
* | | internal: remove more of the SyntaxRewriterAleksey Kladov2021-05-141-29/+31
| | |
* | | internal: remove one more immutable treeAleksey Kladov2021-05-145-54/+33
| | |
* | | Address commentshi-rustin2021-05-143-3/+25
| | |
* | | Apply async semantic token modifier to async/await keywordshi-rustin2021-05-145-0/+17
| | | | | | | | | | | | Only async semantic token modifier
* | | Merge #8830bors[bot]2021-05-132-0/+36
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8830: feat: Implement bulitin macro `concat_idents` r=edwin0cheng a=edwin0cheng cc #8828 bors r+ Co-authored-by: Edwin Cheng <[email protected]>
| * | | Implement `concat_idents`Edwin Cheng2021-05-132-0/+36
| | | |
* | | | Merge #8822bors[bot]2021-05-132-6/+5
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8822: minor: Cleanup imports r=Veykril a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Cleanup importsAleksey Kladov2021-05-132-6/+5
| | | | |
* | | | | Merge #8814bors[bot]2021-05-131-5/+33
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8814: fix: Keep doc comments and outer attrs on "Move module to file" assist r=Veykril a=Jesse-Bakker Fixes #8804 Co-authored-by: Jesse Bakker <[email protected]>
| * | | | | fix: Keep doc comments and outer attrs on "Move module to file" assistJesse Bakker2021-05-131-5/+33
| | |/ / / | |/| | |
* | | | | Merge #8820bors[bot]2021-05-132-2/+37
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8820: fix: Return absolute paths in find_path if crate start is ambiguous r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Wirth <[email protected]>
| * | | | | Return absolute paths in find_path if crate start is ambiguousLukas Wirth2021-05-132-2/+37
| | | | | |
* | | | | | Merge #8823bors[bot]2021-05-131-4/+4
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8823: Enable OPTION::ENABLE_TASKLISTS in pulldown_cmark r=Veykril a=Veykril Closes #8821 Co-authored-by: Lukas Wirth <[email protected]>
| * | | | | | Enable OPTION::ENABLE_TASKLISTS in pulldown_cmarkLukas Wirth2021-05-131-4/+4
| |/ / / / /
* | | | / / Corrected minor typo on line 20mixio2021-05-131-1/+1
| |_|_|/ / |/| | | |
* | | | | Merge #8799bors[bot]2021-05-1212-110/+156
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8799: Add basic support for array lengths in types r=flodiebold a=lf- This recognizes `let a = [1u8, 2, 3]` as having type `[u8; 3]` instead of the previous `[u8; _]`. Byte strings and `[0u8; 2]` kinds of range array declarations are unsupported as before. I don't know why a bunch of our rustc tests had single quotes inside strings un-escaped by `UPDATE_EXPECT=1 cargo t`, but I don't think it's bad? Maybe something in a nightly? Co-authored-by: Jade <[email protected]>
| * | | | | address review by @eddybJade2021-05-112-2/+3
| | | | | |
| * | | | | Add basic support for array lengths in typesJade2021-05-1112-110/+155
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This recognizes `let a = [1u8, 2, 3]` as having type `[u8; 3]` instead of the previous `[u8; _]`. Byte strings and `[0u8; 2]` kinds of range array declarations are unsupported as before. I don't know why a bunch of our rustc tests had single quotes inside strings un-escaped by `UPDATE_EXPECT=1 cargo t`, but I don't think it's bad? Maybe something in a nightly?
* | | | | Merge #8802bors[bot]2021-05-121-9/+126
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8802: Keep comments and attrs when extracting struct from enum variant r=Veykril a=DropDemBits Fixes #6730 Still unsure if existing visibilities of fields should be forced to pub (which is what was previously done), or if it's okay to keep it in the extracted struct. Co-authored-by: DropDemBits <[email protected]>
| * | | | Keep comments and attrs when extracting struct from enum variantDropDemBits2021-05-111-9/+126
| | | | |
* | | | | Fix build script dependenciesJonas Schievink2021-05-123-13/+57
| |_|/ / |/| | |
* | | | Remove delimiters from proc macro inputJonas Schievink2021-05-122-1/+14
| | | |
* | | | Revert "Strip delimiter from fn-like proc macro input"Jonas Schievink2021-05-112-33/+2
| | | | | | | | | | | | | | | | This reverts commit bda68e23328ca62a71da348a13c4d13cc8f991f3.
* | | | Merge #8806bors[bot]2021-05-112-2/+33
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8806: fix: Strip delimiter from fn-like macro invocations r=jonas-schievink a=jonas-schievink This broke in https://github.com/rust-analyzer/rust-analyzer/pull/8796 (again), the fix is easy though bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| * | | | Strip delimiter from fn-like proc macro inputJonas Schievink2021-05-112-2/+33
| | | | |
* | | | | Move `dot` invocation to rust-analyzer crateJonas Schievink2021-05-113-27/+19
|/ / / /
* | | | Use Cargo target name as crate nameJonas Schievink2021-05-111-1/+4
| | | |
* | | | Merge #8398bors[bot]2021-05-116-12/+71
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8398: Fix inference with conditionally compiled tails r=flodiebold a=DJMcNab Fixes #8378 Co-authored-by: Daniel McNab <[email protected]>
| * | | | Add a test for conditionally compiled tailsDaniel McNab2021-05-031-0/+49
| | | | |
| * | | | Fix inference with conditionally compiled tailsDaniel McNab2021-05-035-12/+22
| | | | | | | | | | | | | | | | | | | | Fixes #8378
* | | | | Merge #8801bors[bot]2021-05-116-0/+132
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8801: feat: Allow viewing the crate graph in a webview r=jonas-schievink a=jonas-schievink This uses `dot` to render the crate graph as an SVD file, and displays it in a VS Code panel. For simple crate graphs, it works quite well: ![screenshot-2021-05-11-16:19:32](https://user-images.githubusercontent.com/1786438/117831361-c4a48980-b274-11eb-9276-240cdf6919aa.png) Unfortunately, on rust-analyzer itself (and most medium-sized dependency graphs), `dot` runs for around a minute and then produces this mess: ![screenshot-2021-05-11-16:41:37](https://user-images.githubusercontent.com/1786438/117834831-c754ae00-b277-11eb-850b-138495dbeba8.png) Co-authored-by: Jonas Schievink <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-15 02:23:12 +0000