Remove unused bounds and PhantomData from any and all
#707
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
The phantom data was just plain unneccessary. It was either an oversight or a bug in older rust versions where `SqlType=Array<ST>` didn't count as the type being constrained. The `HasSqlType` constraints are sufficiently covered elsewhere (and frankly, I'm fairly certain that trait is useless and can be removed). It should be noted that we don't have a compile-test covering that case though, as pg is the only backend with additional types.
|
Rolled up into #709 |
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.
The phantom data was just plain unneccessary. It was either an oversight
or a bug in older rust versions where
SqlType=Array<ST>didn't countas the type being constrained. The
HasSqlTypeconstraints aresufficiently covered elsewhere (and frankly, I'm fairly certain that
trait is useless and can be removed). It should be noted that we don't
have a compile-test covering that case though, as pg is the only backend
with additional types.