Better Unpin constraints via impl collision
#31
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
Tamschi
added
help wanted
Tamschi
force-pushed
the
develop
branch
4 times, most recently
from
d180824
to
9a1125c
Compare
|
This can likely be done nicely using const panics now. |
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.
If trait overlap detection was more accurate, it would be possible to forbid unsound
.
Unpinimplementations much more ergonomically (showing a very descriptive trait name with associated documentation in the error). However, this is currently blocked by rust-lang/rust#50551Coherence rules are not consistent when applied to auto traitsAlternatively, this pull request could be made obsolete using
.
constasserts based onmin_specialization, via rust-lang/rust#31844 "Tracking issue for specialization (RFC 1210)"