rust/tests/ui/issues/issue-23122-2.stderr

error[E0275]: overflow evaluating the requirement `<<<<<<<... as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next: Sized`
  --> $DIR/issue-23122-2.rs:12:17
   |
LL |     type Next = <GetNext<T::Next> as Next>::Next;
   |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`issue_23122_2`)
note: required for `GetNext<<<<<<<... as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next>` to implement `Next`
  --> $DIR/issue-23122-2.rs:11:15
   |
LL | impl<T: Next> Next for GetNext<T> {
   |      -        ^^^^     ^^^^^^^^^^
   |      |
   |      unsatisfied trait bound introduced here
   = note: the full type name has been written to '$TEST_BUILD_DIR/issues/issue-23122-2/issue-23122-2.long-type-hash.txt'

error: aborting due to previous error

For more information about this error, try `rustc --explain E0275`.
revert-overflow 2022-11-19 19:43:12 +00:00			error[E0275]: overflow evaluating the requirement `<<<<<<<... as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next: Sized`
new unstable option: -Zwrite-long-types-to-disk This option guards the logic of writing long type names in files and instead using short forms in error messages in rustc_middle/ty/error behind a flag. The main motivation for this change is to disable this behaviour when running ui tests. This logic can be triggered by running tests in a directory that has a long enough path, e.g. /my/very-long-path/where/rust-codebase/exists/ This means ui tests can fail depending on how long the path to their file is. Some ui tests actually rely on this behaviour for their assertions, so for those we enable the flag manually. 2023-07-20 15:47:42 +00:00			`--> $DIR/issue-23122-2.rs:12:17`
Update tests 2019-02-23 22:25:30 +00:00			`\|`
			`LL \| type Next = <GetNext<T::Next> as Next>::Next;`
Use a more accurate span on assoc types WF checks 2021-08-06 15:46:20 +00:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
Update tests 2019-02-23 22:25:30 +00:00			`\|`
Improve help for recursion limit errors 2021-09-28 20:16:42 +00:00			= help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`issue_23122_2`)
fix test 2022-11-26 20:24:58 +00:00			note: required for `GetNext<<<<<<<... as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next as Next>::Next>` to implement `Next`
new unstable option: -Zwrite-long-types-to-disk This option guards the logic of writing long type names in files and instead using short forms in error messages in rustc_middle/ty/error behind a flag. The main motivation for this change is to disable this behaviour when running ui tests. This logic can be triggered by running tests in a directory that has a long enough path, e.g. /my/very-long-path/where/rust-codebase/exists/ This means ui tests can fail depending on how long the path to their file is. Some ui tests actually rely on this behaviour for their assertions, so for those we enable the flag manually. 2023-07-20 15:47:42 +00:00			`--> $DIR/issue-23122-2.rs:11:15`
revert-overflow 2022-11-19 19:43:12 +00:00			`\|`
			`LL \| impl<T: Next> Next for GetNext<T> {`
Note predicate span on ImplDerivedObligation 2023-01-11 03:21:11 +00:00			`\| - ^^^^ ^^^^^^^^^^`
			`\| \|`
			`\| unsatisfied trait bound introduced here`
fix test err 2022-11-19 20:26:42 +00:00			`= note: the full type name has been written to '$TEST_BUILD_DIR/issues/issue-23122-2/issue-23122-2.long-type-hash.txt'`
Update tests 2019-02-23 22:25:30 +00:00
Separate bounds and predicates for associated/opaque types 2020-06-27 20:36:35 +00:00			`error: aborting due to previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			For more information about this error, try `rustc --explain E0275`.