handled ubiqutous Move bounds printing - #1
Open
zannabianca1997 wants to merge 3 commits into
Open
Conversation
it should give some info tho...
Do we need this? I feel like it's important to make notice that a dyn trait misses such an important thing still need to test it as the compiler ICE when creating an immoble type
zannabianca1997
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
for pr rust-lang#156018
First time running through the codebase so I might have missed a better place where to put the filters
last commit adds a
+ !Movebound for types that are not move. I felt it was important to keep that info but I am not sure about itAlso, I guess this should be extended to a category of traits? as there will be the same problem with
ForgetI guess