-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"error: trait bound is not satisfied" when it is #43580
Comments
I believe is the crux of the problem. We don't (yet) support matching HRTB bounds like that. |
@eddyb Thanks for taking a look. Could you elaborate on what you mean by "matching HRTB bounds"? I thought you were referring to the constraint that both lifetimes must be the same, |
I mean the fact that it's a higher ranked bound, i.e. that it has any |
Hey, we are currently running into the same bug. It mostly manifests in code that uses traits mixed with concrete types. It is hard to find the root cause of it, but as we are also having I can not provide any easy to replicate code sample. If wanted, I could point to branches/code in our code bases https://github.com/paritytech/substrate and https://github.com/paritytech/polkadot. |
@nikomatsakis Do you happen to know if this is a duplicate of #30472? |
Not sure off the top of my head, would have to investigate more |
STR
Expected outcome
I would expect this to compile since the supposedly unsatisfied trait bound is right there in the where clause of
claim
.Meta
cc @eddyb @nagisa Any clue what's wrong here? Seems closure related. If you drop the
FnOnce
bound and replaceF
withMaximum<..>
it compiles.The text was updated successfully, but these errors were encountered: