aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* refactor requirements put forward mkladovDmitry2020-08-141-1/+1
|
* restrict visibility only by crateDmitry2020-08-142-2/+2
|
* Revert "replase sparse-checkout by github api"Dmitry2020-08-141-5/+1
| | | | This reverts commit 034db28c542c04b22147da6722328bc74ff99386.
* replase sparse-checkout by github apiDmitry2020-08-141-1/+5
|
* remove fmt skip attrDmitry2020-08-101-1/+1
|\
| * refactoring to show more clearly the import problemsDmitry2020-08-091-5/+5
| |
* | refactoring to show more clearly the import problemsDmitry2020-08-091-5/+5
|/
* Revert "fixes"Dmitry2020-08-091-5/+5
| | | | This reverts commit b602c73911864a86c94d8b306648738f5f995167.
* add skip for generate fileDmitry2020-08-091-1/+1
|
* fixesDmitry2020-08-091-5/+5
|
* apply formatDmitry2020-08-092-5/+9
|
* fix trailing spaceDmitry2020-08-091-1/+1
|
* fix unusedDmitry2020-08-091-1/+0
|
* Merge remote-tracking branch 'origin/master'Dmitry2020-08-09462-6421/+6459
|\
| * Merge #5684bors[bot]2020-08-086-20/+122
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | 5684: Semantic highlighting for unsafe union field access r=jonas-schievink a=Nashenas88 This change adds support for unions in inference and lowering, then extends on that to add the unsafe semantic modifier on field access only. The `is_possibly_unsafe` function in `syntax_highlighting.rs` could be extended to support fns and static muts so that their definitions are not highlighted as unsafe, but only their usage. Also, each commit of this PR updates the tests. By reviewing the files by commit, it's easy to see how the changes in the code affected the tests. Co-authored-by: Paul Daniel Faria <[email protected]>
| | * Apply unsafe semantic highlighting to union field accessPaul Daniel Faria2020-08-082-13/+59
| | |
| | * Add support for unions in inference and loweringPaul Daniel Faria2020-08-084-11/+17
| | |
| | * Add additional checks for union inference testsPaul Daniel Faria2020-08-081-5/+33
| | |
| | * Add test for unsafe union field access highlightingPaul Daniel Faria2020-08-072-0/+22
| | |
| * | Remove cloneVeetaha2020-08-081-1/+1
| | |
| * | Merge #5679bors[bot]2020-08-071-3/+35
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5679: Account for static mut in missing unsafe diagnostic r=jonas-schievink a=Nashenas88 Accessing or modifying a static mut is an unsafe operation. The "missing unsafe" diagnostic now tracks this. Co-authored-by: Paul Daniel Faria <[email protected]>
| | * | Account for static mut in missing unsafe diagnosticPaul Daniel Faria2020-08-071-3/+35
| | |/
| * | Merge #5678bors[bot]2020-08-074-2/+17
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5678: Static mut unsafe semantic highlighting r=jonas-schievink a=Nashenas88 This marks static mutable names as unsafe, since accessing or modifying a static mut is an unsafe operation. Co-authored-by: Paul Daniel Faria <[email protected]>
| | * | Mark static mutable names as unsafePaul Daniel Faria2020-08-073-4/+5
| | | |
| | * | Add test for accessing static mutPaul Daniel Faria2020-08-072-0/+14
| | |/
| * | Merge #5674bors[bot]2020-08-071-3/+3
| |\ \ | | |/ | |/| | | | | | | | | | | | | | | | 5674: Update chalk r=matklad a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| | * Update chalkJeremy Kolb2020-08-061-3/+3
| | |
| * | Merge #5526bors[bot]2020-08-067-14/+208
| |\ \ | | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | 5526: Handle semantic token deltas r=kjeremy a=kjeremy This basically takes the naive approach where we always compute the tokens but save space sending over the wire which apparently solves some GC problems with vscode. This is waiting for https://github.com/gluon-lang/lsp-types/pull/174 to be merged. I am also unsure of the best way to stash the tokens into `DocumentData` in a safe manner. Co-authored-by: kjeremy <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| | * Address PR commentsJeremy Kolb2020-08-064-18/+12
| | |
| | * Handle semantic token deltaskjeremy2020-08-017-13/+213
| | |
| * | Merge #5672bors[bot]2020-08-0512-28/+29
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5672: align names in make r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| | * | align names in makeAleksey Kladov2020-08-0512-28/+29
| | | |
| * | | Merge #5639bors[bot]2020-08-054-6/+68
| |\ \ \ | | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | 5639: SSR: Allow `self` in patterns. r=jonas-schievink a=davidlattimore It's now consistent with other variables in that if the pattern references self, only the `self` in scope where the rule is invoked will be accepted. Since `self` doesn't work the same as other paths, this is implemented by restricting the search to just the current function. Prior to this change (since path resolution was implemented), having self in a pattern would just result in no matches. Co-authored-by: David Lattimore <[email protected]>
| | * | Use SyntaxNode.ancestors instead of a loopDavid Lattimore2020-08-051-7/+1
| | | |
| | * | SSR: Allow `self` in patterns.David Lattimore2020-08-014-6/+74
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | It's now consistent with other variables in that if the pattern references self, only the `self` in scope where the rule is invoked will be accepted. Since `self` doesn't work the same as other paths, this is implemented by restricting the search to just the current function. Prior to this change (since path resolution was implemented), having self in a pattern would just result in no matches.
| * | Merge #5648bors[bot]2020-08-055-1/+425
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5648: Add expand glob import assist r=jonas-schievink a=unexge closes https://github.com/rust-analyzer/rust-analyzer/issues/5557 Co-authored-by: unexge <[email protected]>
| | * | Pattern match on slice elements instead of using `.first().unwrap()`unexge2020-08-051-7/+6
| | | |
| | * | Look for trait methods in expand glob import assistunexge2020-08-051-13/+65
| | | |
| | * | Simplify `find_mod_path` with use of `node.ancestors`unexge2020-08-031-20/+1
| | | |
| | * | Generate doctestunexge2020-08-022-1/+28
| | | |
| | * | Rename ast::UseItem to ast::Useunexge2020-08-021-1/+1
| | | |
| | * | Add expand glob import assistunexge2020-08-024-1/+366
| | | |
| * | | Merge #5664bors[bot]2020-08-053-4/+29
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5664: Fix renamed self module. r=jonas-schievink a=Nashenas88 Fixes #5663 Now `inner_mod` below is properly marked as a `module`. ```rust use crate::inner::{self as inner_mod}; mod inner {} ``` Co-authored-by: Paul Daniel Faria <[email protected]>
| | * | | When resolving a rename, fallback to the name higher in the use tree if the ↵Paul Daniel Faria2020-08-042-4/+23
| | | | | | | | | | | | | | | | | | | | path segment is `self`
| | * | | Add test showing unresolved module renamePaul Daniel Faria2020-08-042-1/+7
| | | | |
| * | | | Use salsa's purge to account for all memoryAleksey Kladov2020-08-053-10/+25
| | | | |
| * | | | Fix relative path handling for custom rustfmtAleksey Kladov2020-08-051-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `current_dir` and relative paths to executables works differently on unix and windows (unix behavior does not make sense), see: https://github.com/oconnor663/duct.rs/blob/17e30e83a16b202551df4d70d0b2cc174cb53e5d/src/lib.rs#L295-L324 The original motivation to set cwd was to make rustfmt read the correct rustfmt.toml, but that was future proofing, rather than a bug fix. So, let's just remove this and see if breaks or fixes more use-cases. If support for per-file config is needed, we could use `--config-path` flag.
| * | | | Merge #5658bors[bot]2020-08-042-1/+44
| |\ \ \ \ | | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5658: do not add to `pub use` in assists that insert a use statement r=jonas-schievink a=jbr closes #5657 , see issue for rationale Initially I wrote a version of this that changed the signature of `insert_use_statement` to take an `Option<VisibilityKind>` and only add to use statements with the same visibility, but that didn't make sense for any of the current uses of `insert_use_statement` (they all expected private visibility). Co-authored-by: Jacob Rothstein <[email protected]>
| | * | | do not add to `pub use` statementsJacob Rothstein2020-08-032-1/+44
| | | | |
| * | | | Revert "Restore line index micro-optimization"Michael Lazear2020-08-032-31/+23
| |/ / / | | | | | | | | | | | | This reverts commit 83a87fcd11298d8de32801ac6496ddf8b4e9c0e1.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-25 19:35:57 +0000