summaryrefslogtreecommitdiff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorDylan DPC <99973273+Dylan-DPC@users.noreply.github.com>2023-05-13 11:05:33 +0530
committerGitHub <noreply@github.com>2023-05-13 11:05:33 +0530
commit05ca3e31df8366578d61f35a29a17bf48b20ac48 (patch)
treece777f5458807add2f4d2d2a84393d365d0c33c4 /tests/rustdoc-js-std/parser-errors.js
parent36125c43da00a2c57452e72c3cf81b71b13de208 (diff)
parent14bf909e71209fc946f35ffba8ae6572c9575715 (diff)
downloadrust-05ca3e31df8366578d61f35a29a17bf48b20ac48.tar.gz
Rollup merge of #111451 - compiler-errors:note-cast-origin, r=b-naber
Note user-facing types of coercion failure When coercing, for example, `Box<A>` into `Box<dyn B>`, make sure that any failure notes mention *those* specific types, rather than mentioning inner types, like "the cast from `A` to `dyn B`". I expect end-users are often confused when we skip layers of types and only mention the "innermost" part of a coercion, especially when other notes point at HIR, e.g. #111406.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions