Remove lots of noise from function signatures #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
theotherphil
added a commit
that referenced
this pull request
Oct 11, 2015
Remove lots of noise from function signatures
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uncontroversial: removing unnecessary 'static bounds.
Controversial: VecBuffer type alias, which produces a compiler warning about bounds not being checked in type aliases. The warning is spurious in this case as using the Subpixel associated type in the right of the definition means the bound is actually checked (I checked this by creating my own trait with matching associated type names and the compiler rejected it).