missing_const_for_fn
: consider constness of instance
#14759
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.
When determining when a function or method can be called from a
const
context, the determination must be made on the instance, not on the declaration. This makes a difference, for example, withconst_trait
traits whose implementations may or may not beconst
.changelog: [
missing_const_for_fn
]: when checking if a function or method can be called from aconst
context, look at the concrete implementation rather than at the trait definitionFixes #14658
r? @Jarcho