Skip to content

Conversation

@nikomatsakis
Copy link
Contributor

Only consider impliciy unboxed closure impl if the obligation is actually for Fn, FnMut, or FnOnce.

Fixes #18019

r? @pcwalton

detected (correctly) that there was only one impl and hence ignored the
`Self` bound completely. I (semi-arbitrarily) elected to delect the
impl, forcing the trait matcher to be more conservative and lean on the
where clauses in scope, yielding the original error message.
bors added a commit that referenced this pull request Oct 17, 2014
Only consider impliciy unboxed closure impl if the obligation is actually for `Fn`, `FnMut`, or `FnOnce`.

Fixes #18019

r? @pcwalton
bors added a commit that referenced this pull request Oct 18, 2014
Only consider impliciy unboxed closure impl if the obligation is actually for `Fn`, `FnMut`, or `FnOnce`.

Fixes #18019

r? @pcwalton
@bors bors closed this Oct 18, 2014
@bors bors merged commit f4a7d32 into rust-lang:master Oct 18, 2014
@nikomatsakis nikomatsakis deleted the issue-18019 branch March 30, 2016 16:13
lnicola pushed a commit to lnicola/rust that referenced this pull request Sep 25, 2024
feat: IDE support for `asm!` expressions

Fixes rust-lang/rust-analyzer#10461, Fixes rust-lang/rust-analyzer#6031 Progresses rust-lang/rust-analyzer#11621

Notably this only works for asm expressions not items yet. Most IDE features work, mainly completions need extra logic still.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Multidispatch inference failure

4 participants