Add new pattern: use custom traits to avoid complex type bounds #437
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.
Introducing traits as an abstraction should be obvious enough in many Rust projects. However, I often found myself introduce "random" type bounds involving
Fn
that would grow unwieldy first until I finally introduced a new trait. So maybe this is advise some people, especially new Rust users, will find useful.I did not include a Motivation section because I felt it was redundant. I also did not (yet) write a Discussion section. There are probably some similar uses of type classes in functional programming languages that we could refer to.