aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_expand
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove fixed FIXME, propagate errors betterJonas Schievink2020-11-241-6/+2
|
* hir_expand: propagate expansion errorsJonas Schievink2020-11-242-41/+84
|
* Fill the diagnostic code field in publish_diagnosticsLukas Wirth2020-11-171-1/+1
|
* SimplifyAleksey Kladov2020-11-061-1/+1
|
* Remove more unreachable pubsAleksey Kladov2020-11-021-1/+1
|
* Fix typo in commentFrancesco Zardi2020-10-211-1/+1
|
* Add whitelist of safe intrinsicsFrancesco Zardi2020-10-211-0/+36
|
* Complete methods when receiver is a macroAleksey Kladov2020-10-171-0/+1
|
* Shorten type hints for std::iter IteratorsLukas Wirth2020-10-061-0/+1
|
* Merge #6033bors[bot]2020-09-281-14/+25
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 6033: Make name resolution resolve proc macros instead of relying purely on the build system r=matklad a=jonas-schievink This makes name resolution look at proc-macro declaration attributes like `#[proc_macro_derive]` and defines the right proc macro in the macro namespace, fixing unresolved custom derives like `thiserror::Error` (which can cause false positives, now that we emit diagnostics for unresolved imports). This works even when proc-macro support is turned off, in which case we fall back to a dummy expander that always returns an error. IMO this is the right way to handle at least the name resolution part of proc. macros, while the *expansion* itself should rely on the build system to build and provide the macro DLL. It does mean that they may go out of sync, but we can provide diagnostics if that happens (something like "could not find macro X in crate Y – ensure that all files of crate Y are saved"). I think it is valuable to be able to reason about proc macros even when we can't expand them, since proc macro expansion can break between Rust releases or users might not want to turn it on for performance reasons. It allows us to provide better diagnostics on any proc macro invocation we're not expanding (like a weak warning that informs the user that proc macro support is turned off, or that it has been disabled because the server crashed). Fixes https://github.com/rust-analyzer/rust-analyzer/issues/5763 Co-authored-by: Jonas Schievink <[email protected]>
| * Use hir_def to resolve proc macrosJonas Schievink2020-09-181-14/+25
| |
* | Bump smol_str from 0.1.16 to 0.1.17Jean SIMARD2020-09-241-5/+5
|/
* Rename `CustomDerive` to `ProcMacro`Jonas Schievink2020-09-184-5/+5
| | | | | It handles fn-like macros too, and will handle attribute macros in the future
* Bump token expansion limitAleksey Kladov2020-09-011-1/+1
| | | | | | | We hit this for redis crate, reported at Reported at https://www.reddit.com/r/rust/comments/ikfsf8/rustanalyzer_doesnt_work_with_the_redis_crate/
* Add description for crates that will be publishedPavan Kumar Sunkara2020-08-241-0/+1
|
* Add version to deps in cargo.tomlPavan Kumar Sunkara2020-08-241-8/+8
|
* Add type safety to diagnostic codesAleksey Kladov2020-08-181-1/+10
|
* Merge branch 'master' into add-disable-diagnosticsIgor Aleksanov2020-08-141-0/+1
|
* Rename ra_hir_expand -> hir_expandAleksey Kladov2020-08-1313-0/+3017