Esteban Küber
413bfa4b98
Wording changes to object unsafe trait errors
...
Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-02-02 11:53:10 -08:00
Mathias Blikstad
ef5acdeceb
RFC 2027: "first draft" of implementation
...
These are a squashed series of commits.
2019-10-22 15:24:33 -04:00
Esteban Küber
efe85943b3
account for DUMMY_SP and correct wording
2019-09-02 22:11:29 -07:00
Esteban Küber
c1e5e5c567
On object safety violation, point at source when possible
2019-09-02 20:22:22 -07:00
memoryruins
eb4580a570
Update ui test suite to use dyn
2019-05-29 00:57:31 -04:00
Andy Russell
b6f148c8bd
hide --explain hint if error has no extended info
2019-04-18 13:29:28 -04:00
Vadim Petrochenkov
fa72a81bea
Update tests
2019-03-11 23:10:26 +03:00
Mark Rousskov
2a663555dd
Remove licenses
2018-12-25 21:08:33 -07:00
Andy Russell
6474de904c
make non_camel_case_types an early lint
2018-12-24 12:58:52 -05:00
Michael Hewson
a0f23f8405
update tests that have changed output
...
I’m not sure why these tests have different output now, but they do.
In all cases, the error message that is missing looks like this: “the
trait bound `dyn Trait: Trait` is not satisfied”
My guess is that the error message is going away because object-safety
now involves trait solving, and these extra error messages are no
longer leaking out.
2018-11-01 18:16:22 -04:00
Matthew Russo
79afc6e9e8
updates tests to use new error code
2018-08-24 08:51:25 -04:00
varkor
aa3b5c58e4
Fix diagnostic regression
2018-08-20 16:16:39 +01:00
varkor
b5c2470ba3
Update new ui tests
2018-08-20 00:08:01 +01:00
David Wood
3fc7ab2373
Merged migrated compile-fail tests and ui tests. Fixes #46841 .
2018-08-14 11:12:09 +02:00
