| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Rename `parse_macro` to `parse_macro_expansion` | Jonas Schievink | 2020-11-24 | 2 | -4/+4 | |
| | | | | | This does not parse macros, it expands a macro and parses the *result* | |||||
| * | hir_expand::db: reduce fn visibility | Jonas Schievink | 2020-11-24 | 1 | -15/+9 | |
| | | ||||||
| * | Remove fixed FIXME, propagate errors better | Jonas Schievink | 2020-11-24 | 1 | -6/+2 | |
| | | ||||||
| * | hir_expand: propagate expansion errors | Jonas Schievink | 2020-11-24 | 2 | -41/+84 | |
| | | ||||||
| * | Fill the diagnostic code field in publish_diagnostics | Lukas Wirth | 2020-11-17 | 1 | -1/+1 | |
| | | ||||||
| * | Simplify | Aleksey Kladov | 2020-11-06 | 1 | -1/+1 | |
| | | ||||||
| * | Remove more unreachable pubs | Aleksey Kladov | 2020-11-02 | 1 | -1/+1 | |
| | | ||||||
| * | Fix typo in comment | Francesco Zardi | 2020-10-21 | 1 | -1/+1 | |
| | | ||||||
| * | Add whitelist of safe intrinsics | Francesco Zardi | 2020-10-21 | 1 | -0/+36 | |
| | | ||||||
| * | Complete methods when receiver is a macro | Aleksey Kladov | 2020-10-17 | 1 | -0/+1 | |
| | | ||||||
| * | Shorten type hints for std::iter Iterators | Lukas Wirth | 2020-10-06 | 1 | -0/+1 | |
| | | ||||||
| * | Merge #6033 | bors[bot] | 2020-09-28 | 1 | -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 macros | Jonas Schievink | 2020-09-18 | 1 | -14/+25 | |
| | | | ||||||
| * | | Bump smol_str from 0.1.16 to 0.1.17 | Jean SIMARD | 2020-09-24 | 1 | -5/+5 | |
| |/ | ||||||
| * | Rename `CustomDerive` to `ProcMacro` | Jonas Schievink | 2020-09-18 | 4 | -5/+5 | |
| | | | | | | It handles fn-like macros too, and will handle attribute macros in the future | |||||
| * | Bump token expansion limit | Aleksey Kladov | 2020-09-01 | 1 | -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 type safety to diagnostic codes | Aleksey Kladov | 2020-08-18 | 1 | -1/+10 | |
| | | ||||||
| * | Merge branch 'master' into add-disable-diagnostics | Igor Aleksanov | 2020-08-14 | 1 | -0/+1 | |
| | | ||||||
| * | Rename ra_hir_expand -> hir_expand | Aleksey Kladov | 2020-08-13 | 12 | -0/+2994 | |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |