@WG-prioritization/alerts issue #79033 has been requested for prioritization.
I-nominated
?I would mark this as P-medium
like the sister issue mentioned (#41078)
I kind of think this should be P-high
(disclaimer: I'm the author of the issue). On stable, the error is:
expected
&Location<'_>
, found&Location<'_>
but nightly (maybe beta too now), shows:
expected
(&Location<'_>,)
, found(&Location<'_>,)
which I find quite weird. The error is weird enough as it is since it shows two things that are equal, but it's even weirder that it has changed to showing tuples on nightly. I'm guessing the reason the two things look equal but are not is because of constraints on inference variables? I don't know enough about the type-checker to know for sure though.
bump, unprioritized
I think P-medium since it's a diagnostics bug with a workaround
Issue #79033's prioritization request has been removed.