diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-11-28 15:10:00 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-11-28 15:10:00 +0000 |
| commit | 7f3ba7d57fd2f43f3cfc012f898a26d940bf5cc8 (patch) | |
| tree | 8262e9c458f5b1a120422c89962f7cf37a97cb69 /crates/syntax/test_data/parser/fragments/item/err | |
| parent | b7ece77af49ce59762fc3246a4c721411efe637e (diff) | |
| parent | d171838d63907d004ab935d6564bfeb4238d5540 (diff) | |
Merge #6645
6645: Publish diagnostics for macro expansion errors r=matklad a=jonas-schievink
This adds 2 new diagnostics, emitted during name resolution:
* `unresolved-proc-macro`, a weak warning that is emitted when a proc macro is supposed to be expanded, but was not provided by the build system. This usually means that proc macro support is turned off, but may also indicate setup issues when using rust-project.json. Being a weak warning, this should help set expectations when users see it, while not being too obstructive. We do not yet emit this for attribute macros though, just custom derives and `!` macros.
* `macro-error`, which is emitted when any macro (procedural or `macro_rules!`) fails to expand due to some error. This is an error-level diagnostic, but currently still marked as experimental, because there might be spurious errors and this hasn't been tested too well.
This does not yet emit diagnostics when expansion in item bodies fails, just for module-level macros.
Known bug: The "proc macro not found" diagnostic points at the whole item for custom derives, it should just point at the macro's name in the `#[derive]` list, but I haven't found an easy way to do that.
Screenshots:
Co-authored-by: Jonas Schievink <[email protected]>
Diffstat (limited to 'crates/syntax/test_data/parser/fragments/item/err')
0 files changed, 0 insertions, 0 deletions