Fix an inference failure (fn found, different fn expected.
)
#184
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the latest nightly (rust-lang/rust@62fb41c32) I get an error such as:
I believe this is introduced by rust PR#19891
If you look closely you'll see rustc has tagged the expected fn-ptr with the name of the function from the first match-arm:
expected``(_, fn(&[u8], aesni::KeyType, &mut [u8]) {aesni::setup_working_key_aesni_128})``
This patch declares a type without that tag and then uses that type in lieu of the inference.
Reading that PR: I do think we need to be explicit about the expected type here to trigger the coercion we want.