aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * Add doc comment for resolve_hir_path_qualifierHasan Ali2020-05-161-0/+13
| |
| * Fix completion and hover for module and function of same nameHasan Ali2020-05-164-2/+102
| |
* | Chalk upgradeFlorian Diebold2020-05-162-22/+41
| |
* | Add 'self to parameter' renaming.zbsz2020-05-161-5/+206
|/
* Handle `Self` in values and patternsFlorian Diebold2020-05-156-19/+197
| | | | | | | | | I.e. - `Self(x)` or `Self` in tuple/unit struct impls - `Self::Variant(x)` or `Self::Variant` in enum impls - the same in patterns Fixes #4454.
* Merge #4448bors[bot]2020-05-151-1/+4
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4448: Generate configuration for launch.json r=vsrs a=vsrs This PR adds two new commands: `"rust-analyzer.debug"` and `"rust-analyzer.newDebugConfig"`. The former is a supplement to the existing `"rust-analyzer.run"` command and works the same way: asks for a runnable and starts new debug session. The latter allows adding a new configuration to **launch.json** (or to update an existing one). If the new option `"rust-analyzer.debug.useLaunchJson"` is set to true then `"rust-analyzer.debug"` and Debug Lens will first look for existing debug configuration in **launch.json**. That is, it has become possible to specify startup arguments, env variables, etc. `"rust-analyzer.debug.useLaunchJson"` is false by default, but it might be worth making true the default value. Personally I prefer true, but I'm not sure if it is good for all value. ---- I think that this PR also solves https://github.com/rust-analyzer/rust-analyzer/issues/3441. Both methods to update launch.json mentioned in the issue do not work: 1. Menu. It is only possible to add a launch.json configuration template via a debug adapter. And anyway it's only a template and it is impossible to specify arguments from an extension. 2. DebugConfigurationProvider. The exact opposite situation: it is possible to specify all debug session settings, but it is impossible to export these settings to launch.json. Separate `"rust-analyzer.newDebugConfig"` command looks better for me. ---- Fixes #4450 Fixes #3441 Co-authored-by: vsrs <[email protected]> Co-authored-by: vsrs <[email protected]>
| * Better label for a runnable.vsrs2020-05-141-1/+1
| | | | | | Co-authored-by: Aleksey Kladov <[email protected]>
| * Multiple binaries support for launch.json.vsrs2020-05-141-1/+4
| | | | | | | | Generate unique names on the LSP side.
* | Merge #4431bors[bot]2020-05-153-3/+37
|\ \ | | | | | | | | | | | | | | | | | | | | | 4431: Store proc-macro result in salsa db r=matklad a=edwin0cheng Fixed #4315 Co-authored-by: Edwin Cheng <[email protected]>
| * | Store proc-macro result in salsa dbEdwin Cheng2020-05-143-3/+37
| | |
* | | CleanupsAleksey Kladov2020-05-152-85/+75
| | |
* | | Better structureAleksey Kladov2020-05-153-19/+15
| | |
* | | Move LSP bits from flycheck to rust-analyzerAleksey Kladov2020-05-1517-1504/+1503
| | | | | | | | | | | | | | | There should be only one place that knows about LSP, and that place is right before we spit JSON on stdout.
* | | Merge #4273bors[bot]2020-05-142-4/+532
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4273: Trigger add_vis assist on paths/record fields as well r=flodiebold a=TimoFreiberg Resolves #4037. - [x] Function defs - [x] ADT defs - [x] Enum variants - [x] Consts - [x] Statics - [x] Traits - [x] Type aliases - [x] Modules - [x] Record fields (using different implementation) - [x] struct fields - [x] enum variant fields - :x: union fields (`Semantics::resolve_record_field` seems to not work for union fields, so I think this can be handled in a future PR) - [x] More tests? - [x] Improve test fixture code and documentation a bit (see [Zulip](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/resolve_path.20between.20fixture.20files)) Co-authored-by: Timo Freiberg <[email protected]>
| * | | Expand fixture documentation a littleTimo Freiberg2020-05-101-3/+17
| | | |
| * | | Trigger change_visibility assist when on an invisible struct fieldTimo Freiberg2020-05-101-61/+248
| | | | | | | | | | | | | | | | Union fields apparently don't work :(
| * | | Trigger change_visibility assist when on a path to an invisible defTimo Freiberg2020-05-101-1/+328
| | | |
* | | | MinorAleksey Kladov2020-05-141-10/+8
| | | |
* | | | Put preselect items on topAleksey Kladov2020-05-141-1/+3
| | | |
* | | | Prioritize locals with correct typesAleksey Kladov2020-05-142-5/+55
| | | |
* | | | Merge #4445bors[bot]2020-05-145-2/+92
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4445: Correctly fill default type parameters r=flodiebold a=montekki Fixes #3877 So, basically even if the parameters are omitted from the `impl` block, check the parameters in `trait` if they have a default type, and if they do go from `hir` to `ast::TypeArg`. I've added a helper for that but I am not sure that it's a proper way to go from `hir` to `ast` here. Co-authored-by: Fedor Sakharov <[email protected]>
| * | | | Ty -> TypeFedor Sakharov2020-05-141-2/+7
| | | | |
| * | | | Adds a param_idx helperFedor Sakharov2020-05-142-2/+7
| | | | |
| * | | | Fix formattingFedor Sakharov2020-05-141-1/+1
| | | | |
| * | | | Change type_arg to type_ref funcFedor Sakharov2020-05-142-4/+3
| | | | |
| * | | | Use generic_defaults and display_source_codeFedor Sakharov2020-05-143-13/+16
| | | | |
| * | | | Correctly fill default type parametersFedor Sakharov2020-05-135-1/+79
| | | | |
* | | | | Merge #4405bors[bot]2020-05-145-9/+6
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4405: Make some stuff public so that they can be reused by other tools r=pksunkara a=pksunkara So, my little experiment of building a code analysis tool using rust-analyzer is successful. I am going to proceed to build the tool now. This PR makes the needed things public. I know there were some things about trying to change stuff regarding loading workspaces, which would make it more easier for other tools to reuse. But, until then, it should be okay using this `load_cargo` fn. Btw, if I were publish my tool, I would need the `ra` crates to be released. Since @matklad told me that he doesn't want to care about breaking stuff, I would propose the following. Every monday, during the weekly release, we release a new pre v1 minor version of all the crates. That way, we don't need to care about breaking stuff but still have rust-analyzer on crates.io. I made https://github.com/pksunkara/cargo-workspaces to help release workspace crates easily. So, coming week, we start with `0.1.0`, then week after that, we release `0.2.0` and then `0.3.0` etc.. until we decide on `1.0.0` which is probably when the compiler team also starts using the crates. There is no limit to the minor versions (we can even have `0.150.0` or `0.1500.0`), so I don't see anything wrong with this strategy. Co-authored-by: Pavan Kumar Sunkara <[email protected]>
| * | | | Make some stuff public so that they can be reused by other toolsPavan Kumar Sunkara2020-05-145-9/+6
| | | | |
* | | | | Use back ticks instead of single quotes around codeTrevor Spiteri2020-05-144-4/+4
|/ / / /
* / / / Remove hidden VARIATION SELECTOR-16Laurențiu Nicola2020-05-131-2/+2
|/ / /
* | | Merge #4434bors[bot]2020-05-131-15/+43
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4434: add more specific match postfix for Result and Option r=matklad a=bnjjj In order to have the same behavior than `if let` and `while let` Co-authored-by: Benjamin Coenen <[email protected]>
| * | | add more specific match postfix for Result and OptionBenjamin Coenen2020-05-121-15/+43
| | | | | | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
* | | | Merge #4083bors[bot]2020-05-131-138/+1366
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4083: Smol documentation for ast nodes r=matklad a=Veetaha There is a tremendous amount of TODOs to clarify the topics I am not certain about. Please @matklad, @edwin0cheng review carefully, I even left some mentions of your names in todos to put your attention where you most probably can give comments. In order to simplify the review, I separated the codegen (i.e. changes in `ast/generated/nodes.rs`) from `ast_src` changes (they in fact just duplicate one another) into two commits. Also, I had to hack a little bit to let the docs be generated as doc comments and not as doc attributes because it's easier to read them this way and IIRC we don't support hints for `#[doc = ""]` attributes for now... Closes #3682 Co-authored-by: veetaha <[email protected]>
| * | | | Remove an equals sign from `ConstArg` (this probably pertains only to ↵veetaha2020-05-121-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ConstParam) (As per matklad)
| * | | | Convert TODO to a Note(matklad)veetaha2020-05-121-0/+1
| | | | |
| * | | | Convert to TODOs to FIXMEs as per matkladveetaha2020-05-121-4/+2
| | | | |
| * | | | Revert "Remove MacroStmts as per edwin0cheng" (cc @edwin0cheng) and add a ↵veetaha2020-05-121-0/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fixme to document it. This reverts commit 7a49165f5d5c8186edd04f874eae8a98e39d3df6. MacroStmts ast node is not used by itself, but it pertains to SyntaxNodeKind MACRO_STMTS that is used by ra_paser, so even tho the node itself is not used, it is better to keep it with a FIXME to actually add a doc comment when it becomes useful.
| * | | | Add a doc comment on the difference between Name and NameRef ast nodesveetaha2020-05-121-1/+16
| | | | |
| * | | | Resolve TODO about macro 2.0 defveetaha2020-05-101-6/+4
| | | | |
| * | | | Fix typoveetaha2020-05-101-1/+1
| | | | |
| * | | | Carify on a semicolon in macro callveetaha2020-05-101-1/+6
| | | | |
| * | | | Resolve TODO about curly-braced constructions in expression statementveetaha2020-05-101-1/+3
| | | | |
| * | | | Resolve todos about refs and empty statementsveetaha2020-05-101-4/+4
| | | | |
| * | | | Converted TODO about MacroItems to FIXME as per edwin0chengveetaha2020-05-101-6/+2
| | | | |
| * | | | Verified ConstArg example, waiting for response on what `=` sign pertains toveetaha2020-05-101-1/+1
| | | | |
| * | | | Correcy use tree and type args docsveetaha2020-05-101-3/+3
| | | | |
| * | | | Correct `use` cannot have type args as per flodieboldveetaha2020-05-101-1/+1
| | | | |
| * | | | Correct path docs and add colon2 token to Path ast nodeveetaha2020-05-101-8/+14
| | | | |
| * | | | Add example with const in TypeBound as per flodieboldveetaha2020-05-101-1/+1
| | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 12:53:47 +0000