Don't ICE on unconstrained anonymous lifetimes inside associated types.

[smmalis37]

Fixes#62200. The change here is inspired (copied) by how this case is handled on bare fns at

rust/src/librustc_typeck/astconv.rs

Lines 3083 to 3106 in e8b55a4

	for br in late_bound_in_ret.difference(&late_bound_in_args){
	let lifetime_name = match*br {
	ty::BrNamed(_, name) => format!("lifetime `{}`,", name),
	ty::BrAnon(_) | ty::BrEnv => "an anonymous lifetime".to_string(),
	};
	letmut err = struct_span_err!(
	tcx.sess,
	decl.output.span(),
	E0581,
	"return type references {} which is not constrained by the fn input types",
	lifetime_name
	);
	iflet ty::BrAnon(_) = *br {
	// The only way for an anonymous lifetime to wind up
	// in the return type but **also** be unconstrained is
	// if it only appears in "associated types" in the
	// input. See #47511 for an example. In this case,
	// though we can easily give a hint that ought to be
	// relevant.
	err.note(
	"lifetimes appearing in an associated type are not considered constrained",
	);
	}
	err.emit();

.

[rust-highfive]

r? @davidtwco

(rust_highfive has picked a reviewer for you, use r? to override)

[davidtwco]

@bors r+

[bors]

📌 Commit bbaab63 has been approved by davidtwco

[bors]

⌛ Testing commit bbaab63 with merge e9d67a3cd88b7a8350112e69507668a7c71ac50d...

[rust-log-analyzer]

The job dist-i686-msvc of your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @rust-lang/infra. (Feature Requests)

[bors]

💔 Test failed - checks-actions

[davidtwco]

@rust-lang/infra @rust-log-analyzer's snippet is empty in the above comment - the error seems spurious too.

[ehuss]

@bors retry
rust-lang/cargo#8517