aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* Add testsZac Pullar-Strecker2020-10-081-2/+94
|
* Update tests for new function fieldZac Pullar-Strecker2020-10-081-12/+12
|
* Change Option::Some bug to a fixme noteZac Pullar-Strecker2020-10-082-3/+4
| | | | IMO this is too much work to be worth fixing at the moment.
* Differentiate method/tymethod by determining 'defaultness'Zac Pullar-Strecker2020-10-086-8/+30
| | | | | | | | | Currently a method only has defaultness if it is a provided trait method, but this will change when specialisation is available and may need to become a concept known to hir. I opted to go for a 'fewest changes' approach given specialisation is still under development.
* Code reorganisation and field supportZac Pullar-Strecker2020-10-084-56/+101
|
* Changes from reviewZac Pullar-Strecker2020-10-085-37/+13
|
* Rename ide::link_rewrite -> ide::doc_links & tidy importsZac Pullar-Strecker2020-10-083-4/+4
|
* Add support for struct & trait methodsZac Pullar-Strecker2020-10-081-7/+83
|
* WIP: Command to open docs under cursorZac Pullar-Strecker2020-10-085-2/+132
|
* Merge #6161bors[bot]2020-10-073-3/+19
|\ | | | | | | | | | | | | | | 6161: Bump chalk to use latest git to get upstream fix r=jonas-schievink a=Ameobea * Chalk very recently (like an hour ago) merged a fix that prevents rust analyzer from panicking. This allows it to be usable again for code that hits those situations. See #6134, #6145, Probably #6120 Co-authored-by: Casey Primozic <[email protected]>
| * Switch from git to latest tagged release of chalk depsCasey Primozic2020-10-071-3/+3
| |
| * Make unimplemented match variants explicitCasey Primozic2020-10-071-1/+2
| |
| * `todo!()` -> `unimplemented!() // FIXME` for CICasey Primozic2020-10-062-3/+5
| |
| * Bump chalk to use latest git to get fixCasey Primozic2020-10-063-3/+16
| | | | | | | | * Chalk very recently (like an hour ago) merged a fix that prevents rust analyzer from panicking. This allows it to be usable again for code that hits those situations. See #6134, #6145, Probably #6120
* | Merge #6154bors[bot]2020-10-075-56/+295
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6154: Shorten type hints for std::iter Iterators r=SomeoneToIgnore a=Veykril Fixes #3750. This re-exports the `hir_expand::name::known` module to be able to fetch the `Iterator` and `iter` names. I'm not sure if there is anything to do with `Solution::Ambig` in `normalize_trait_assoc_type` or whether discarding those results is always wanted. Co-authored-by: Lukas Wirth <[email protected]>
| * | Clean up inlay_hintsLukas Wirth2020-10-072-19/+26
| | |
| * | Shorten iterator hints for std::iter iterators behind referencesLukas Wirth2020-10-072-3/+5
| | |
| * | Shorten iterator chain hintsLukas Wirth2020-10-072-43/+115
| | |
| * | Move IntoIterator into FamousDefsLukas Wirth2020-10-072-31/+20
| | |
| * | Use FamousDefs for shorten_iterator hintLukas Wirth2020-10-062-69/+85
| | |
| * | Shorten type hints for std::iter IteratorsLukas Wirth2020-10-064-9/+162
| | |
* | | Better progress APIAleksey Kladov2020-10-072-4/+9
| | | | | | | | | | | | | | | | | | Percentage is a UI concern, the physical fact here is fraction. It's sad that percentage bleeds into the protocol level, we even duplicated this bad API ourselves!
* | | CleanupAleksey Kladov2020-10-072-22/+23
| | |
* | | Merge #6158bors[bot]2020-10-071-5/+33
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6158: Fix for negative literals in macros r=matklad a=cutsoy _This pull request fixes #6028._ When writing `-42.0f32` in Rust, it is usually parsed as two different tokens (a minus operator and a float literal). But a procedural macro can also generate new tokens, including negative [float literals](https://doc.rust-lang.org/stable/proc_macro/struct.Literal.html#method.f32_suffixed): ```rust #[proc_macro] fn example_verbose(input: TokenStream) -> TokenStream { let literal = Literal::f32_suffixed(-42.0); quote! { #literal } } ``` or even shorter ```rust #[proc_macro] fn example(input: TokenStream) -> TokenStream { let literal = -42.0f32; quote! { #literal } } ``` Unfortunately, these currently cause RA to crash: ``` thread '<unnamed>' panicked at 'Fail to convert given literal Literal { text: "-42.0f32", id: TokenId( 4294967295, ), }', crates/mbe/src/subtree_source.rs:161:28 ``` This pull request contains both a fix 8cf9362 and a unit test 27798ee. In addition, I installed the patched server with `cargo xtask install --server` and verified in VSCode that it no longer crashes when a procedural macro returns a negative number literal. Co-authored-by: Tim <[email protected]>
| * | | Added unit test for negative number literals in macros.Tim2020-10-061-0/+21
| | | |
| * | | Fixed parsing of negative number literals in macros.Tim2020-10-061-5/+12
| | |/ | |/|
* | | Merge #6160bors[bot]2020-10-075-1/+448
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 6160: Add validation check for ambiguous trait objects r=matklad a=Veykril Fixes #285. Co-authored-by: Lukas Wirth <[email protected]>
| * | Add validation check for ambiguous trait objectsLukas Wirth2020-10-065-1/+448
| | |
* | | Merge #6128bors[bot]2020-10-061-4/+25
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6128: Trim all trailing whitespace in onEnter r=matklad a=repnop Fixes #5848 Co-authored-by: Wesley Norris <[email protected]>
| * | | Trim all trailing whitespace in onEnterWesley Norris2020-10-031-4/+25
| | | | | | | | | | | | | | | | Fixes #5848
* | | | Document privacy invariant of SyntaxPtrAleksey Kladov2020-10-061-0/+2
| | | |
* | | | Merge #6140bors[bot]2020-10-065-9/+81
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6140: honour hover.content_format client capability r=lnicola a=robinvd This removes all markdown when the client does not support the markdown MarkupKind. Otherwise the output on the editor will have some markdown boilerplate, making it less readable. For example kak_lsp does not currently support markdown. ![image](https://user-images.githubusercontent.com/22073483/95112949-ef0ff080-0741-11eb-82a7-0594fa2cd736.png) after: ![image](https://user-images.githubusercontent.com/22073483/95113089-2bdbe780-0742-11eb-94fa-bcfec6d7347a.png) Co-authored-by: Robin van Dijk <[email protected]>
| * | | | add break after codeblocksRobin van Dijk2020-10-061-2/+4
| | | | |
| * | | | add doc describing limited capabilitiesRobin van Dijk2020-10-061-0/+2
| | | | |
| * | | | add docstringRobin van Dijk2020-10-051-0/+3
| | | | |
| * | | | honor content_format clientcapRobin van Dijk2020-10-055-9/+74
| |/ / / | | | | | | | | | | | | | | | | | | | | This removes all markdown when the client does not support the markdown MarkupKind Otherwise the output on the editor will have some markdown boilerplate, making it less readable
* | | / Add test makrAleksey Kladov2020-10-061-0/+2
| |_|/ |/| |
* | | Constrain ImportMap to only store simple pathsAleksey Kladov2020-10-061-10/+26
| | |
* | | Merge #6150bors[bot]2020-10-068-46/+65
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6150: Move ModPath->ast::Path function to IDE layer r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Move ModPath->ast::Path function to IDE layerAleksey Kladov2020-10-068-46/+65
| | |/ | |/| | | | | | | closes #6092
* | | Merge #6148bors[bot]2020-10-062-6/+57
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 6148: Fix trait object hir formatting behind pointer and references r=matklad a=Veykril Fixes #6064 Co-authored-by: Lukas Wirth <[email protected]>
| * | 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
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-13 17:37:26 +0000