rust/src/test/ui/allocator, branch perf-tmp

Move /src/test to /tests

2023-01-11T09:32:08+00:00

Reduce the number of unstable features in tests

2022-11-30T15:55:10+00:00

Stabilize default_alloc_error_handler

2022-11-03T07:12:58+00:00

Closes #66741

Fix a bunch of typo

2022-08-31T10:24:55+00:00

This PR will fix some typos detected by [typos]. I only picked the ones I was sure were spelling errors to fix, mostly in the comments. [typos]: https://github.com/crate-ci/typos

Warn about dead tuple struct fields

2022-08-03T10:17:23+00:00

Mention implementers of unsatisfied trait

2022-04-04T21:01:42+00:00

When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that *do* implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 | LL | impl Baz for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz where U: Foo { } | ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`.

Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`

2021-12-15T01:40:08+00:00

Do not mention associated items when they introduce an obligation

2021-11-20T19:19:31+00:00

Various diagnostics clean ups/tweaks

2021-07-19T15:43:35+00:00

* Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition

Show macro name in 'this error originates in macro' message

2021-05-12T23:03:06+00:00

When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.