aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* Add workaround for changing sysroot pathsLaurențiu Nicola2020-07-301-8/+34
|
* Update testsAleksey Kladov2020-07-303-5/+5
|
* Finish extern crates grammarAleksey Kladov2020-07-306-70/+70
|
* Merge #5584bors[bot]2020-07-301-1/+1
|\ | | | | | | | | | | | | | | | | | | | | 5584: Rename metric r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Rename metricAleksey Kladov2020-07-301-1/+1
| |
* | Update testsAleksey Kladov2020-07-304-11/+15
| |
* | Rename RenameAleksey Kladov2020-07-309-16/+16
| |
* | Finish Module grammarAleksey Kladov2020-07-301-0/+1
| |
* | Update testsAleksey Kladov2020-07-3033-40/+40
| |
* | Split ItemList & AssocItemListAleksey Kladov2020-07-3012-78/+118
|/
* FixesAleksey Kladov2020-07-301-11/+1
|
* Fix non-linux compilationAleksey Kladov2020-07-302-6/+25
|
* Do not show progress with parallel analysisAleksey Kladov2020-07-301-0/+1
|
* Report instructions in addition to timeAleksey Kladov2020-07-304-20/+95
| | | | They hopefully will be more stable on CI
* fix castAleksey Kladov2020-07-301-1/+1
|
* Allow negative bytesAleksey Kladov2020-07-302-23/+23
| | | | Gotta be optimistic about those memory usage optimizations
* Drop resident from memory usageAleksey Kladov2020-07-301-4/+3
|
* Merge #5578bors[bot]2020-07-2917-464/+459
|\ | | | | | | | | | | | | | | | | | | | | 5578: Rename ModuleItem -> Item r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Finish SourceFile grammarAleksey Kladov2020-07-292-2/+4
| |
| * Rename ModuleItem -> ItemAleksey Kladov2020-07-2916-462/+455
| |
* | Merge #5554bors[bot]2020-07-291-9/+85
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5554: Fix remove_dbg r=matklad a=petr-tik Closes #5129 Addresses two issues: - keep the parens from dbg!() in case the call is chained or there is semantic difference if parens are excluded - Exclude the semicolon after the dbg!(); by checking if it was accidentally included in the macro_call investigated, but decided against: fix ast::MacroCall extraction to never include semicolons at the end - this logic lives in rowan. Defensively shorten the macro_range if there is a semicolon token. Deleted unneccessary temp variable macro_args Renamed macro_content to "paste_instead_of_dbg", because it isn't a simple extraction of text inside dbg!() anymore Co-authored-by: petr-tik <[email protected]>
| * | Addressed code reviewpetr-tik2020-07-291-27/+41
| | | | | | | | | | | | | | | | | | | | | replaced match with let-if variable assignment removed the unnecessary semicolon_on_end variable converted all code and expected test variables to raw strings and inlined them in asserts
| * | Fixed #5129petr-tik2020-07-271-8/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Addresses two issues: - keep the parens from dbg!() in case the call is chained or there is semantic difference if parens are excluded - Exclude the semicolon after the dbg!(); by checking if it was accidentally included in the macro_call investigated, but decided against: fix ast::MacroCall extraction to never include semicolons at the end - this logic lives in rowan. Defensively shorten the macro_range if there is a semicolon token. Deleted unneccessary temp variable macro_args Renamed macro_content to "paste_instead_of_dbg", because it isn't a simple extraction of text inside dbg!() anymore
| * | Make all test fn names consistent in remove_dbgpetr-tik2020-07-271-3/+29
| | |
| * | Added failing testspetr-tik2020-07-271-0/+21
| | |
* | | Merge #5563bors[bot]2020-07-292-6/+7
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | 5563: Check all targets for package-level tasks r=matklad a=SomeoneToIgnore When invoking "Select Runnable" with the caret on a runnable with a specific target (test, bench, binary), append the corresponding argument for the `cargo check -p` module runnable. Co-authored-by: Kirill Bulatov <[email protected]>
| * | Run package-specific cargo check and test for all targetsKirill Bulatov2020-07-292-6/+7
| | |
* | | cargo_metadata 0.11.1 and cargo updatekjeremy2020-07-293-3/+3
| | |
* | | Update crates/rust-analyzer/src/cli/analysis_stats.rsAleksey Kladov2020-07-291-1/+1
| | | | | | | | | Co-authored-by: LaurenČ›iu Nicola <[email protected]>
* | | Replace rand with oorandomAleksey Kladov2020-07-295-18/+33
| | |
* | | Rename NomialDef -> AdtDefAleksey Kladov2020-07-294-27/+27
| | |
* | | Switch to ungrammar from ast_srcAleksey Kladov2020-07-294-2205/+825
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The primary advantage of ungrammar is that it (eventually) allows one to describe concrete syntax tree structure -- with alternatives and specific sequence of tokens & nodes. That should be re-usable for: * generate `make` calls * Rust reference * Hypothetical parser's evented API We loose doc comments for the time being unfortunately. I don't think we should add support for doc comments to ungrammar -- they'll make grammar file hard to read. We might supply docs as out-of band info, or maybe just via a reference, but we'll think about that once things are no longer in flux
* | | Dead codeAleksey Kladov2020-07-291-41/+0
| | |
* | | Remove dead codeAleksey Kladov2020-07-291-3/+1
| | |
* | | Remove dead codeAleksey Kladov2020-07-291-46/+0
|/ /
* | Merge #5564bors[bot]2020-07-299-53/+182
|\ \ | | | | | | | | | | | | | | | | | | | | | 5564: SSR: Restrict to current selection if any r=davidlattimore a=davidlattimore The selection is also used to avoid unnecessary work, but only to the file level. Further restricting unnecessary work is left for later. Co-authored-by: David Lattimore <[email protected]>
| * | SSR: Rename position and lookup_context to resolve_contextDavid Lattimore2020-07-292-6/+6
| | |
| * | SSR: Restrict to current selection if anyDavid Lattimore2020-07-298-48/+177
| | | | | | | | | | | | | | | The selection is also used to avoid unnecessary work, but only to the file level. Further restricting unnecessary work is left for later.
* | | Merge #5565bors[bot]2020-07-292-1/+62
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5565: SSR: Don't mix non-path-based rules with path-based r=matklad a=davidlattimore If any rules contain paths, then we reject any rules that don't contain paths. Allowing a mix leads to strange semantics, since the path-based rules only match things where the path refers to semantically the same thing, whereas the non-path-based rules could match anything. Specifically, if we have a rule like `foo ==>> bar` we only want to match the `foo` that is in the current scope, not any `foo`. However "foo" can be parsed as a pattern (BIND_PAT -> NAME -> IDENT). Allowing such a rule through would result in renaming everything called `foo` to `bar`. It'd also be slow, since without a path, we'd have to use the slow-scan search mechanism. Co-authored-by: David Lattimore <[email protected]>
| * | | SSR: Don't mix non-path-based rules with path-basedDavid Lattimore2020-07-292-1/+62
| |/ / | | | | | | | | | If any rules contain paths, then we reject any rules that don't contain paths. Allowing a mix leads to strange semantics, since the path-based rules only match things where the path refers to semantically the same thing, whereas the non-path-based rules could match anything. Specifically, if we have a rule like `foo ==>> bar` we only want to match the `foo` that is in the current scope, not any `foo`. However "foo" can be parsed as a pattern (BIND_PAT -> NAME -> IDENT). Allowing such a rule through would result in renaming everything called `foo` to `bar`. It'd also be slow, since without a path, we'd have to use the slow-scan search mechanism.
* / / Allow running more tests at onceKirill Bulatov2020-07-281-54/+110
|/ /
* | Fix nameref parsingAleksey Kladov2020-07-283-7/+8
| |
* | Bump test timeout for macsAleksey Kladov2020-07-281-1/+2
| |
* | Merge #5547bors[bot]2020-07-271-1/+13
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5547: Fold multiline fn parameters r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Fold multiline fn parametersAleksey Kladov2020-07-271-1/+13
| | |
* | | Merge #5532bors[bot]2020-07-272-23/+31
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 5532: Restore line index optimization for edits r=matklad a=lnicola Co-authored-by: LaurenČ›iu Nicola <[email protected]>
| * | Restore line index micro-optimizationLaurențiu Nicola2020-07-252-23/+31
| | |
* | | Merge #5539bors[bot]2020-07-273-27/+103
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5539: SSR: Fix path resolution of locals in current scope r=matklad a=davidlattimore Co-authored-by: David Lattimore <[email protected]>
| * | | SSR: Fix for path resolution of localsDavid Lattimore2020-07-262-0/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It seems that Semantics::scope, if given a statement node, won't resolve locals that were defined in the current scope, only in parent scopes. Not sure if this is intended / expected behavior, but we work around it for now by finding another nearby node to use as the scope (e.g. the expression inside the EXPR_STMT).
| * | | SSR: Move more resolution-related code into the resolving moduleDavid Lattimore2020-07-262-27/+38
| | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-30 00:21:31 +0000