about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorDylan DPC <99973273+Dylan-DPC@users.noreply.github.com>2022-11-11 20:51:38 +0530
committerGitHub <noreply@github.com>2022-11-11 20:51:38 +0530
commitbc9567fbf67977621663612450dc16a9fd4262a6 (patch)
tree0ae4d6b662e806664ae1dc1fcc409a8a7e52a4a6 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent978e7abeceed3c4d0d6c729c9e492890f478e8e1 (diff)
parent449a4404f5216a085cc0aa89042b39a4bdff5b51 (diff)
downloadrust-bc9567fbf67977621663612450dc16a9fd4262a6.tar.gz
rust-bc9567fbf67977621663612450dc16a9fd4262a6.zip
Rollup merge of #103445 - fmease:fix-50291, r=estebank
`#[test]`: Point at return type if `Termination` bound is unsatisfied

Together with #103142 (already merged) this fully fixes #50291.

I don't consider my current solution of changing a few spans “here and there” very clean since the
failed obligation is a `FunctionArgumentObligation` and we point at a type instead of a function argument.

If you agree with me on this point, I can offer to keep the spans of the existing nodes and instead inject
`let _: AssertRetTyIsTermination<$ret_ty>;` (type to be defined in `libtest`) similar to `AssertParamIsEq` etc.
used by some built-in derive-macros.

I haven't tried that approach yet though and cannot promise that it would actually work out or
be “cleaner” for that matter.

````@rustbot```` label A-libtest A-diagnostics
r? ````@estebank````
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions