feat: support generic fn params without static bound #61
+261
−85
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.
fixes #52
This is the implementation for #52, which supports fn generic bounds like
fn method<T>(&self, arg: T)
, whereT
does not have a'static
bound.It is technically a breaking change, because more trait definitions now require explicit
'static
bounds, e.g. the code example from #37. Even if the bound trait that has an implicit'static
super-bound, unimock now requires an extra explicit bound regardless.I'm unsure if this change is desired, so the PR will be left open for a while.