rust-analyzer - [FORK] modified to work on wasm targets

	Commit message (Collapse)	Author	Age	Files	Lines
...
\| * \|	"rust-analyzer.newDebugConfig" command	vsrs	2020-05-11	4	-3/+36
\| \| \|
\| * \|	"rust-analyzer.debug" command	vsrs	2020-05-11	4	-106/+144
\| \| \|
* \| \|	Merge #4431	bors[bot]	2020-05-15	3	-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 db	Edwin Cheng	2020-05-14	3	-3/+37
\| \| \| \|
* \| \| \|	Merge #4460	bors[bot]	2020-05-15	18	-1506/+1490
\|\ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4460: Remove flycheck -> LSP dependency r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
\| * \| \| \|	Cleanups	Aleksey Kladov	2020-05-15	2	-85/+75
\| \| \| \| \|
\| * \| \| \|	Better structure	Aleksey Kladov	2020-05-15	4	-20/+15
\| \| \| \| \|
\| * \| \| \|	Move LSP bits from flycheck to rust-analyzer	Aleksey Kladov	2020-05-15	18	-1506/+1505
\|/ / / / \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	There should be only one place that knows about LSP, and that place is right before we spit JSON on stdout.
* \| \| \|	Merge #4273	bors[bot]	2020-05-14	2	-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 little	Timo Freiberg	2020-05-10	1	-3/+17
\| \| \| \| \|
\| * \| \| \|	Trigger change_visibility assist when on an invisible struct field	Timo Freiberg	2020-05-10	1	-61/+248
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Union fields apparently don't work :(
\| * \| \| \|	Trigger change_visibility assist when on a path to an invisible def	Timo Freiberg	2020-05-10	1	-1/+328
\| \| \| \| \|
* \| \| \| \|	Merge #4456	bors[bot]	2020-05-14	1	-11/+11
\|\ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4456: Sort preselect items on top r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
\| * \| \| \| \|	Minor	Aleksey Kladov	2020-05-14	1	-10/+8
\| \| \| \| \| \|
\| * \| \| \| \|	Put preselect items on top	Aleksey Kladov	2020-05-14	1	-1/+3
\| \| \| \| \| \|
* \| \| \| \| \|	Merge #4455	bors[bot]	2020-05-14	2	-5/+55
\|\\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4455: Prioritize locals with correct types r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
\| * \| \| \| \|	Prioritize locals with correct types	Aleksey Kladov	2020-05-14	2	-5/+55
\|/ / / / /
* \| \| \| \|	Merge #4445	bors[bot]	2020-05-14	5	-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 -> Type	Fedor Sakharov	2020-05-14	1	-2/+7
\| \| \| \| \| \|
\| * \| \| \| \|	Adds a param_idx helper	Fedor Sakharov	2020-05-14	2	-2/+7
\| \| \| \| \| \|
\| * \| \| \| \|	Fix formatting	Fedor Sakharov	2020-05-14	1	-1/+1
\| \| \| \| \| \|
\| * \| \| \| \|	Change type_arg to type_ref func	Fedor Sakharov	2020-05-14	2	-4/+3
\| \| \| \| \| \|
\| * \| \| \| \|	Use generic_defaults and display_source_code	Fedor Sakharov	2020-05-14	4	-14/+16
\| \| \| \| \| \|
\| * \| \| \| \|	Correctly fill default type parameters	Fedor Sakharov	2020-05-13	6	-1/+80
\| \| \| \| \| \|
* \| \| \| \| \|	Merge #4405	bors[bot]	2020-05-14	6	-10/+7
\|\ \ \ \ \ \ \| \|_\|_\|/ / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 tools	Pavan Kumar Sunkara	2020-05-14	6	-10/+7
\| \| \| \| \| \|
* \| \| \| \| \|	Merge #4432	bors[bot]	2020-05-14	1	-2/+12
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4432: Update features.md r=matklad a=bnjjj Co-authored-by: Coenen Benjamin <[email protected]>
\| * \| \| \| \| \|	Update features.md	Coenen Benjamin	2020-05-12	1	-2/+12
\| \| \| \| \| \| \|
* \| \| \| \| \| \|	Merge #4452	bors[bot]	2020-05-14	4	-4/+4
\|\ \ \ \ \ \ \ \| \|_\|/ / / / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4452: Use back ticks instead of single quotes around code r=matklad a=tspiteri Also, use back ticks instead of single quotes in `rustc_unescape_error_to_string` for `EE:UnclosedUnicodeEscape`. Co-authored-by: Trevor Spiteri <[email protected]>
\| * \| \| \| \| \|	Use back ticks instead of single quotes around code	Trevor Spiteri	2020-05-14	4	-4/+4
\|/ / / / / /
* \| \| \| \| \|	Merge #4447	bors[bot]	2020-05-13	1	-2/+2
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4447: Remove VARIATION SELECTOR-16 in Run arrow r=matklad a=lnicola Closes #4446, cc @Veetaha. Co-authored-by: Laurențiu Nicola <[email protected]>
\| * \| \| \| \| \|	Remove hidden VARIATION SELECTOR-16	Laurențiu Nicola	2020-05-13	1	-2/+2
\| \| \| \| \| \| \|
* \| \| \| \| \| \|	Merge #4400	bors[bot]	2020-05-13	1	-0/+3
\|\ \ \ \ \ \ \ \| \|_\|_\|/ / / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4400: Enhanced coloring r=georgewfraser a=georgewfraser This PR builds on #4397 to enhance the existing syntax coloring. ## Underline mutable variables The textmate scope `markup.underline` underlines identifiers, which is a nice way to make mutable vars stand out: <img width="327" alt="Screen Shot 2020-05-09 at 1 18 55 PM" src="https://user-images.githubusercontent.com/1369240/81484179-8bb47d80-91f8-11ea-997d-1dcffbe44aa7.png"> ## Italicize static variables The textmate scope `markup.italic` italicizes identifiers. Italic = static is a common convention in IDEs like IntelliJ: <img width="288" alt="Screen Shot 2020-05-09 at 1 19 14 PM" src="https://user-images.githubusercontent.com/1369240/81484236-cd452880-91f8-11ea-8478-505ee49bc8b3.png"> Co-authored-by: George Fraser <[email protected]>
\| * \| \| \| \| \|	Leave statics alone	George Fraser	2020-05-12	1	-3/+0
\| \| \| \| \| \| \|
\| * \| \| \| \| \|	Mark up statics and mutables	George Fraser	2020-05-12	1	-0/+6
\| \| \| \| \| \| \|
* \| \| \| \| \| \|	Merge #4444	bors[bot]	2020-05-13	1	-6/+6
\|\ \ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4444: Update crates r=kjeremy a=kjeremy Documentation improvements Co-authored-by: kjeremy <[email protected]>
\| * \| \| \| \| \| \|	Update crates	kjeremy	2020-05-13	1	-6/+6
\| \| \|/ / / / / \| \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Documentation improvements
* \| \| \| \| \| \|	Merge #4440	bors[bot]	2020-05-13	2	-51/+59
\|\ \ \ \ \ \ \ \| \|/ / / / / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4440: Update packages r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]>
\| * \| \| \| \| \|	Bump packages	kjeremy	2020-05-13	2	-50/+58
\| \| \| \| \| \| \|
\| * \| \| \| \| \|	vscode engine 1.45	kjeremy	2020-05-12	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	latest stable
* \| \| \| \| \| \|	Merge #4434	bors[bot]	2020-05-13	1	-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 Option	Benjamin Coenen	2020-05-12	1	-15/+43
\| \| \|_\|/ / / / \| \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Signed-off-by: Benjamin Coenen <[email protected]>
* \| \| \| \| \| \|	Merge #4083	bors[bot]	2020-05-13	4	-153/+2877
\|\ \ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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]>
\| * \| \| \| \| \| \|	Convert TODO about ParamList used in closures to a FIXME	veetaha	2020-05-12	1	-2/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	cc @matklad (you didn't comment on this one)
\| * \| \| \| \| \| \|	Remove an equals sign from `ConstArg` (this probably pertains only to ↵	veetaha	2020-05-12	2	-4/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	ConstParam) (As per matklad)
\| * \| \| \| \| \| \|	Remove a comment on NameRefToken as per matklad	veetaha	2020-05-12	1	-1/+1
\| \| \| \| \| \| \| \|
\| * \| \| \| \| \| \|	Convert TODO to a FIXME as per matklad	veetaha	2020-05-12	1	-1/+1
\| \| \| \| \| \| \| \|
\| * \| \| \| \| \| \|	Convert TODO to a Note(matklad)	veetaha	2020-05-12	2	-1/+2
\| \| \| \| \| \| \| \|
\| * \| \| \| \| \| \|	Convert to TODOs to FIXMEs as per matklad	veetaha	2020-05-12	2	-8/+4
\| \| \| \| \| \| \| \|
\| * \| \| \| \| \| \|	Revert "Remove MacroStmts as per edwin0cheng" (cc @edwin0cheng) and add a ↵	veetaha	2020-05-12	2	-0/+45
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.