diff options
| author | bors <bors@rust-lang.org> | 2018-07-14 06:24:42 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-07-14 06:24:42 +0000 |
| commit | 0a8275f8b677304458c6161e26436dfe67ab766b (patch) | |
| tree | a5d160f108f84428c9d9e89fa2768b57393e7e16 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | ccade97544d34f42c37fc27fe8c7edba05d3eddb (diff) | |
| parent | b5c2b79fb21f835fd20f176ca0f9c4d7e89ac095 (diff) | |
| download | rust-0a8275f8b677304458c6161e26436dfe67ab766b.tar.gz rust-0a8275f8b677304458c6161e26436dfe67ab766b.zip | |
Auto merge of #52244 - glandium:issue52097, r=estebank
Don't display default generic parameters in diagnostics that compare types
In errors like:
```
expected type: `RawVec<foo, Global>`
found type: `foo`
```
`RawVec` being defined as `RawVec<T, A: Alloc = Global>`, the error is better written as
```
expected type: `RawVec<foo>`
found type: `foo`
```
In fact, that is already what happens when `foo` is not an ADT, because in that case, the diagnostic handler doesn't try to highlight something, and just uses the `Display` trait instead of its own logic.
e.g.
```
expected type: `RawVec<usize>`
found type: `usize`
```
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
