about summary refs log tree commit diff
path: root/crates/project-model
AgeCommit message (Collapse)AuthorLines
2022-07-19Upgrade to expect-test@1.4.0Amos Wenger-1/+1
cf. https://github.com/rust-analyzer/expect-test/issues/33 cf. https://github.com/rust-lang/rust/pull/99444#issuecomment-1188844202
2022-07-11Fix `rustcSource` -> `rustc_source`TonalidadeHidrica-2/+2
This only fixes the comments in the internal source, which is not mandatory at all
2022-07-08Update remaining GitHub URLsJonas Schievink-1/+1
2022-07-03Bump cargo_metadataLaurențiu Nicola-5/+10
2022-06-28fix: Report proc macro errors in expressions correctly as wellFlorian Diebold-39/+39
They didn't have a krate before, resulting in the generic "proc macro not found" error. Also improve error messages a bit more.
2022-06-24Auto merge of #12520 - Veykril:flycheck-cancel, r=Veykrilbors-1/+1
internal: Bring back JodChild into flychecking for cancellation cc https://github.com/rust-lang/rust-analyzer/pull/10517/files#r895241975
2022-06-24Improve proc macro errors a bitFlorian Diebold-36/+37
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-20Fix testFlorian Diebold-2/+0
2022-06-20Refactor a bitFlorian Diebold-23/+15
2022-06-20Only apply `cfg(test)` for local cratesFlorian Diebold-2/+7
Don't analyze dependencies with `test`; this should fix various cases where crates use `cfg(not(test))` and so we didn't find things. "Local" here currently means anything that's not from the registry, so anything inside the workspace, but also path dependencies. So this isn't perfect, and users might still need to use `rust-analyzer.cargo.unsetTest` for these in some cases.
2022-06-15Update test outputsLukas Wirth-27/+81
2022-06-15Show proc-macro loading errors in unresolved-proc-macro diagnosticsLukas Wirth-20/+19
2022-06-13internal: Bring back JodChild into flychecking for cancellationLukas Wirth-1/+1
2022-06-12fix: Pass the build data to rustc_private cratesLukas Wirth-1/+3
2022-06-10Auto merge of #12502 - Veykril:deps, r=Veykrilbors-6/+6
internal: Bump Dependencies
2022-06-10internal: Bump DependenciesLukas Wirth-6/+6
2022-06-06Remove the unneeded destructuring assignment in `run` in ↵KOLANICH-2/+2
`project-model/src/build_scripts.rs`
2022-06-04Only record build script outputs when the output has been changedLukas Wirth-10/+10
2022-06-03internal: Don't log default build script outputsLukas Wirth-20/+29
2022-05-24minor: log build script invocationsLukas Wirth-8/+3
2022-05-20Don't swallow build script errorsJonas Schievink-17/+17
2022-05-19simplifyJonas Schievink-6/+2
2022-05-14internal: vendor lsp-serverAleksey Kladov-1/+1
2022-05-01style: rename crates to kebab casePeh-0/+4562