aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Fix trait object hir formatting behind pointer and referencesLukas Wirth2020-10-062-6/+57
| |/
* | Merge #6124bors[bot]2020-10-0610-31/+64
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6124: Better normalized crate name usage r=jonas-schievink a=SomeoneToIgnore Closes https://github.com/rust-analyzer/rust-analyzer/issues/5343 Closes https://github.com/rust-analyzer/rust-analyzer/issues/5932 Uses normalized name for code snippets (to be able to test the fix), hover messages and documentation rewrite links (are there any tests for those?). Also renamed the field to better resemble the semantics. Co-authored-by: Kirill Bulatov <[email protected]>
| * | Properly name the fieldKirill Bulatov2020-10-028-24/+26
| | |
| * | Fix the hover dash issuesKirill Bulatov2020-10-024-9/+10
| | |
| * | Add a dash testKirill Bulatov2020-10-022-2/+32
| | |
* | | Merge #6139bors[bot]2020-10-066-118/+172
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6139: Make find_path_prefixed configurable r=matklad a=Veykril This makes `find_path_prefixed` more configurable allowing one to choose whether it always returns absolute paths, self-prefixed paths or to ignore local imports when building the path. The config names are just thrown in here, taking better names if they exist :) This should fix #6131 as well? Co-authored-by: Lukas Wirth <[email protected]>
| * | | Make ImportPrefix a configuration optionLukas Wirth2020-10-055-9/+33
| | | |
| * | | Make find_path_prefixed configurableLukas Wirth2020-10-052-110/+140
| | |/ | |/|
* | | Do not leave braces for colons in dbg!Kirill Bulatov2020-10-061-2/+7
| | |
* | | Merge #6111bors[bot]2020-10-054-5/+738
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6111: Add assist for converting the base of integer literals. r=SomeoneToIgnore a=vlakreeh This PR adds an assist similar to Intellij's [convert number to](https://i.imgur.com/JH6wstP.png). It also does a small refactor to [assists/src/tests.rs](https://github.com/rust-analyzer/rust-analyzer/blob/fc34403018079ea053f26d0a31b7517053c7dd8c/crates/assists/src/tests.rs) to add the ability to specify the resolved assist for a specific action within an assist group. ## Demo ![Demo of the assist in action](https://i.imgur.com/MBhdPFH.gif) Co-authored-by: vlakreeh <[email protected]>
| * | | Add tests for convert integer literal assistvlakreeh2020-09-301-4/+570
| | | |
| * | | Add ability to specify ResolvedAssist by labelvlakreeh2020-09-291-5/+22
| | | |
| * | | Add convert integer literal assistvlakreeh2020-09-293-0/+150
| | | |
* | | | Account for proc macro helpers when parsing attrJonas Schievink2020-10-052-1/+9
| | | |
* | | | Merge #6127bors[bot]2020-10-052-2/+23
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6127: Correctly complete items with leading underscore r=SomeoneToIgnore a=fmease Fixes #6091. Let me know if the test is placed into the right file or if it is even desired. Co-authored-by: León Orell Valerian Liehr <[email protected]>
| * | | | Correctly complete items with leading underscoreLeón Orell Valerian Liehr2020-10-032-2/+23
| | | | |
* | | | | Fix feature nameAleksey Kladov2020-10-051-1/+1
| |_|/ / |/| | |
* | | | Improve readability in inlay_hints.rsIgor Aleksanov2020-10-031-4/+5
| | | |
* | | | Remove 'for_expr' test from inlay_hints.rsIgor Aleksanov2020-10-031-14/+1
| | | |
* | | | Make the tests for complete/incomplete for inlay hints workIgor Aleksanov2020-10-031-10/+77
| | | |
* | | | Better inlay hints in 'for' loopsIgor Aleksanov2020-10-031-2/+49
|/ / /
* | / Simplify ast_transformAleksey Kladov2020-10-021-40/+34
| |/ |/|
* | rename mock_analysis -> fixtureAleksey Kladov2020-10-0223-99/+90
| |
* | Get rid of MockAnalysisAleksey Kladov2020-10-0219-420/+288
| |
* | Rewrite fixtures on top of ChangeAleksey Kladov2020-10-021-83/+90
| |
* | Move ide::AnalysisChange -> base_db::ChangeAleksey Kladov2020-10-0211-93/+122
| | | | | | | | | | | | This seems like a better factoring logically; ideally, clients shouldn't touch `set_` methods of the database directly. Additionally, I think this should remove the unfortunate duplication in fixture code.
* | Expectify find_references testsAleksey Kladov2020-10-021-176/+181
| |
* | Reduce visibiityAleksey Kladov2020-10-022-13/+14
| |
* | Merge #5988bors[bot]2020-10-023-2/+338
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5988: Postfix completions for fmt-like string literals r=matklad a=popzxc This pull request adds a bunch of new postfix completions for `format`-like string literls. For example, `"{32} {some_var:?}".println` will expand to `println!("{} {:?}", 32, some_var)`. Postfix completions were added for most common format-like macros: - `println` -> `println!(...)` - `fmt` -> `format!(...)` - `panic` -> `panic!(...)` - `log` macros: + `logi` -> `log::info!(...)` + `logw` -> `log::warn!(...)` + `loge` -> `log::error!(...)` + `logt` -> `log::trace!(...)` + `logd` -> `log::debug!(...)` ![fmt_postfix](https://user-images.githubusercontent.com/12111581/92998650-a048af80-f523-11ea-8fd8-410146de8caa.gif) Co-authored-by: Igor Aleksanov <[email protected]>
| * | Use expect_test to make format_str_parser test more data-drivenIgor Aleksanov2020-10-021-35/+35
| | |
| * | Use lookup table instead of enum for postfix completion kindsIgor Aleksanov2020-10-021-62/+20
| | |
| * | Use ast::String for extracting string literal contentsIgor Aleksanov2020-10-022-14/+19
| | |
| * | Improve format-like completions code appearanceIgor Aleksanov2020-10-022-32/+26
| | |
| * | Add missing entry to doc-commentIgor Aleksanov2020-10-021-0/+1
| | |
| * | Simplify is_string_literal functionIgor Aleksanov2020-10-021-9/+5
| | |
| * | Improve checks for postfix suggestionsIgor Aleksanov2020-10-023-16/+23
| | |
| * | Add postfix completion for format-like string literalsIgor Aleksanov2020-10-023-1/+376
| | |
* | | Merge #5954bors[bot]2020-10-025-0/+36
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5954: Add flexible configuration for runnables r=popzxc a=popzxc This PR introduces two new configuration options for runnables: `overrideCargo` and `cargoExtraArgs`. These options are applied to all the "run" tasks of rust analyzer, such as binaries and tests. Overall motivation is that rust-analyzer provides similar options, for example, for `rustfmt`, but not for runnables. ## `overrideCargo` This option allows user to replace `cargo` command with something else (well, something that is compatible with the cargo arguments). Motivation is that some projects may have wrappers around cargo (or even whole alternatives to cargo), which do something related to the project, and only then run `cargo`. With this feature, such users will be able to use lens and run tests directly from the IDE rather than from terminal. ![cargo_override](https://user-images.githubusercontent.com/12111581/92306622-2f404f80-ef99-11ea-9bb7-6c6192a2c54a.gif) ## `cargoExtraArgs` This option allows user to add any additional arguments for `cargo`, such as `--release`. It may be useful, for example, if project has big integration tests which take too long in debug mode, or if any other `cargo` flag has to be passed. ![cargo_extra_args](https://user-images.githubusercontent.com/12111581/92306658-821a0700-ef99-11ea-8be9-bf0aff78e154.gif) Co-authored-by: Igor Aleksanov <[email protected]>
| * | | Fix failing testIgor Aleksanov2020-10-021-0/+6
| | | |
| * | | Replace 'cargo_prefix' option with 'override_cargo'Igor Aleksanov2020-10-024-10/+10
| | | |
| * | | Add support of runnables arguments in Rust AnalyzerIgor Aleksanov2020-10-024-0/+30
| |/ /
* | | Merge #6105bors[bot]2020-10-021-48/+85
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6105: Fix path comparison not comparing paths correctly with unequal lengths r=matklad a=Veykril ~~This PR includes the commit from #6102 there as I found a bug while writing that(so either merging this or both in order works) so I included a test there already which was just ignored.~~ This PR fixes that, basically inserting imports didn't consider path length for equality, so depending on the order it might insert the path before or after another import if they only differ in segment length. ~~Diff without the commit of #6102 https://github.com/rust-analyzer/rust-analyzer/commit/2d90d3937d71f9a00f3d44c15b20679215311637~~ Co-authored-by: Lukas Wirth <[email protected]>
| * | Fix path comparison not comparing paths correctly with unequal lengthsLukas Wirth2020-10-011-48/+85
| | |
* | | Merge #6104bors[bot]2020-10-026-7/+7
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6104: Minor clippy performance suggestions r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * | | Minor clippy performance suggestionskjeremy2020-09-306-7/+7
| | | |
* | | | Up rustc-ap-rustc_lexer to 681kjeremy2020-10-012-5/+5
| |/ / |/| | | | | | | | cargo update as well
* | | Fix MergingBehaviour::Last not working properlyLukas Wirth2020-09-301-21/+52
|/ /
* | Extend **Status** command to also show dep info for the fileAleksey Kladov2020-09-294-21/+59
| | | | | | | | This should help with troubleshooting wrong project configuration
* | Remove periodic gc stubAleksey Kladov2020-09-296-64/+13
| |
* | More panic_contextAleksey Kladov2020-09-291-1/+3
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 15:56:17 +0000