about summary refs log tree commit diff
path: root/src/test/codegen/src-hash-algorithm
diff options
context:
space:
mode:
authorJonas Schievink <jonasschievink@gmail.com>2020-11-10 14:45:09 +0100
committerGitHub <noreply@github.com>2020-11-10 14:45:09 +0100
commit9596e34ad49325c0711b56e9d0797768ee6c907f (patch)
treeaa198e04da3cf78c91230f1fe826bb9ab991bcca /src/test/codegen/src-hash-algorithm
parentcf9cf7c923eb01146971429044f216a3ca905e06 (diff)
parent6be48475fe51ca8dd9ca35d931319e9f3e008c58 (diff)
downloadrust-9596e34ad49325c0711b56e9d0797768ee6c907f.tar.gz
rust-9596e34ad49325c0711b56e9d0797768ee6c907f.zip
Rollup merge of #76765 - guswynn:async_return, r=tmandry
Make it more clear what an about async fn's returns when referring to what it returns

see #76547

This is *likely* not the ONLY place that this happens to be unclear, but we can move this fn to rustc_middle or something like that and reuse it if need be, to apply it to more diagnostics

One outstanding question I have is, if the fn returns (), should I make the message more clear (what about `fn f()` vs `fn f() -> ()`, can you tell those apart in the hir?)

R? `@tmandry`

`@rustbot` modify labels +A-diagnostics +T-compiler
Diffstat (limited to 'src/test/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions