1b416473a3
Upgrade to expect-test@1.4.0
...
cf. https://github.com/rust-analyzer/expect-test/issues/33
cf. https://github.com/rust-lang/rust/pull/99444#issuecomment-1188844202
2022-07-19 13:00:45 +02:00
d2fd137252
Use SmallVec to slightly shrink ModPath size
2022-07-06 19:49:05 +02:00
993a19a19a
Bump the rest of the deps
2022-07-03 10:24:07 +03:00
78beb4c444
Bump chalk
2022-07-03 10:22:10 +03:00
e05e6c60a7
Bump object
2022-07-03 10:14:48 +03:00
5381811368
Bump tracing-subscriber
2022-07-03 10:12:58 +03:00
a3011e5ed2
Bump arbitrary and derive_arbitrary
2022-07-03 10:10:45 +03:00
9e7ca80c82
Bump cargo_metadata
2022-07-03 10:09:35 +03:00
2d3f0b4841
Bump semver
2022-07-03 10:09:35 +03:00
6669f388a2
Bump indexmap
2022-07-03 10:09:35 +03:00
b24ece5220
Bump serde_json
2022-07-03 10:09:35 +03:00
87572bee23
Bump serde
2022-07-03 10:09:35 +03:00
791f2a0bec
Bump smallvec
2022-07-03 10:09:35 +03:00
2af61bc9ba
Bump pulldown-cmark-to-cmark
2022-07-03 10:09:35 +03:00
e6fcb23445
Bump either
2022-07-03 10:09:35 +03:00
c7c314d462
Bump quote
2022-07-03 10:09:35 +03:00
416787d26d
Bump anyhow
2022-07-03 09:57:01 +03:00
212f84ab46
Bump crossbeam-channel
2022-07-03 09:56:58 +03:00
c80c34867f
Improve proc macro errors a bit
...
Distinguish between
- there is no build data (for some reason?)
- there is build data, but the cargo package didn't build a proc macro dylib
- there is a proc macro dylib, but it didn't contain the proc macro we expected
- the name did not resolve to any macro (this is now an
unresolved_macro_call even for attributes)
I changed the handling of disabled attribute macro expansion to
immediately ignore the macro and report an unresolved_proc_macro,
because otherwise they would now result in loud unresolved_macro_call
errors. I hope this doesn't break anything.
Also try to improve error ranges for unresolved_macro_call / macro_error
by reusing the code for unresolved_proc_macro. It's not perfect but
probably better than before.
2022-06-24 13:45:19 +02:00
76ae5434fa
internal: Bump Dependencies
2022-06-10 17:30:02 +02:00
0cf677ab42
internal: Update dashmap and freeze its version
2022-06-10 16:19:52 +02:00
364dd5ff89
Fix build on OpenBSD (and probably other BSDs too)
...
notify-5.0.0-pre.14 does not build on these systems; this was fixed in
https://github.com/notify-rs/notify/commit/41a74f0e98a1af386749ad3be4a197865054f17f , which landed in pre.15.
2022-05-22 17:04:57 -04:00
e64ccddcc7
⬆️ deps
2022-05-19 17:08:18 +01:00
57cb65bb7a
internal: vendor lsp-server
2022-05-14 21:15:43 +01:00
59dcb63309
⬆️ deps
2022-05-03 11:57:40 +01:00
1f011fa4a3
style: rename crates to kebab case
2022-05-01 10:48:58 +00:00
c7396a5c64
Downgrade kqueue to fix NetBSD
2022-04-30 19:02:24 +03:00
4255996965
Re-export FxHashMap and FxHashSet from ide_db
2022-04-25 18:51:59 +02:00
8154365b00
minor: Remove either dependency from ide_completion
2022-04-25 18:40:38 +02:00
117f902d55
Bump deps
2022-04-17 19:36:08 +03:00
e2f1a9a558
feat: Attempt to format expand_macro output with rustfmt if possible
2022-04-17 13:33:39 +02:00
5901eddb02
Bump chalk
2022-04-12 20:10:10 +03:00
2d445de170
minor: bump lsp-server version
2022-04-09 00:13:47 +02:00
c71c30419c
Use bitflags for FnFlags
2022-04-07 16:22:34 +02:00
85f797f59c
Bump chalk
2022-03-27 10:11:02 +03:00
8e91bb7660
minor: Bump dependencies
2022-03-22 17:42:24 +01:00
86b1ef9ab2
Bump deps
2022-03-17 19:24:37 +02:00
be6d5001e4
Bump xshell and fix dist
2022-03-17 08:53:33 +02:00
83575c96ed
Merge #11700
...
11700: ⬆️ xshell r=matklad a=matklad
Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com >
2022-03-14 15:02:34 +00:00
56e43c34e7
⬆️ xshell
2022-03-14 14:57:24 +00:00
b301b040f5
Add const generics
2022-03-14 14:38:37 +03:30
a9dd606387
fix: Show what file paths were expected for unresolved modules
2022-03-11 17:08:30 +01:00
533f178a52
minor: Access parser internals through ide_db for ide crates
2022-03-10 17:07:28 +01:00
c0d6471143
fix: Recognize Self as a proper keyword
2022-03-05 23:20:06 +01:00
8f504dc873
Merge #11598
...
11598: feat: Parse destructuring assignment r=Veykril a=ChayimFriedman2
Part of #11532 .
Lowering is not as easy and may not even be feasible right now as it requires generating identifiers: `(a, b) = (b, a)` is desugared into
```rust
{
let (<gensym_a>, <gensym_b>) = (b, a);
a = <gensym_a>;
b = <gensym_b>;
}
```
rustc uses hygiene to implement that, but we don't support hygiene yet.
However, I think parsing was the main problem as lowering will just affect type inference, and while `{unknown}` is not nice it's much better than a syntax error.
I'm still looking for the best way to do lowering, though.
Fixes #11454 .
Co-authored-by: Chayim Refael Friedman <chayimfr@gmail.com >
2022-03-05 11:31:29 +00:00
d9f0731bd2
Parse destructuring assignment
...
The only patterns we should parse are `..` in structs and `_`: the rest are either not supported or already valid expressions.
2022-03-02 01:51:25 +00:00
96c16bc382
redirct: use iterators and knowledge about preordered arrays for more efficient merging
2022-02-28 05:56:51 +01:00
9881614db1
Upgrade ungrammar to 1.15.0
2022-02-21 08:34:36 +02:00
02904e99ac
Merge #11464
...
11464: minor: Bump deps r=lnicola a=lnicola
bors r+
Co-authored-by: Laurențiu Nicola <lnicola@dend.ro >
2022-02-13 16:15:37 +00:00
60c698bbcf
Bump deps
2022-02-13 18:14:49 +02:00
Amos Wenger