rust/src/test/ui/issues/issue-18611.stderr

error[E0277]: the trait bound `isize: HasState` is not satisfied
  --> $DIR/issue-18611.rs:1:18
   |
LL | fn add_state(op: <isize as HasState>::State) {
   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `HasState` is not implemented for `isize`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			error[E0277]: the trait bound `isize: HasState` is not satisfied
Support HIR wf checking for function signatures During function type-checking, we normalize any associated types in the function signature (argument types + return type), and then create WF obligations for each of the normalized types. The HIR wf code does not currently support this case, so any errors that we get have imprecise spans. This commit extends `ObligationCauseCode::WellFormed` to support recording a function parameter, allowing us to get the corresponding HIR type if an error occurs. Function typechecking is modified to pass this information during signature normalization and WF checking. The resulting code is fairly verbose, due to the fact that we can no longer normalize the entire signature with a single function call. As part of the refactoring, we now perform HIR-based WF checking for several other 'typed items' (statics, consts, and inherent impls). As a result, WF and projection errors in a function signature now have a precise span, which points directly at the responsible type. If a function signature is constructed via a macro, this will allow the error message to point at the code 'most responsible' for the error (e.g. a user-supplied macro argument). 2021-07-18 11:33:49 -05:00			`--> $DIR/issue-18611.rs:1:18`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Replace associated item bound vars with placeholders when projecting. 2021-07-08 23:04:47 -05:00			`LL \| fn add_state(op: <isize as HasState>::State) {`
Support HIR wf checking for function signatures During function type-checking, we normalize any associated types in the function signature (argument types + return type), and then create WF obligations for each of the normalized types. The HIR wf code does not currently support this case, so any errors that we get have imprecise spans. This commit extends `ObligationCauseCode::WellFormed` to support recording a function parameter, allowing us to get the corresponding HIR type if an error occurs. Function typechecking is modified to pass this information during signature normalization and WF checking. The resulting code is fairly verbose, due to the fact that we can no longer normalize the entire signature with a single function call. As part of the refactoring, we now perform HIR-based WF checking for several other 'typed items' (statics, consts, and inherent impls). As a result, WF and projection errors in a function signature now have a precise span, which points directly at the responsible type. If a function signature is constructed via a macro, this will allow the error message to point at the code 'most responsible' for the error (e.g. a user-supplied macro argument). 2021-07-18 11:33:49 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `HasState` is not implemented for `isize`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0277`.