Fix some more unconstrained types in msg_send results#453
Merged
august64 merged 2 commits intorust-windowing:masterfrom Apr 9, 2018
Merged
Fix some more unconstrained types in msg_send results#453august64 merged 2 commits intorust-windowing:masterfrom
august64 merged 2 commits intorust-windowing:masterfrom
Conversation
The error I was investigating servo/servo#20474 (comment) turned out to be already be fixed by rust-windowing#428, but there was a few more cases of the same problem.
Member
|
Thanks! I think this should have a CHANGELOG entry though. |
Contributor
Author
|
I’m already several yaks deep and I don’t directly need this change so this is only a drive-by PR and I won’t work on it further, sorry. Feel free to take over. |
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
2 participants
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 error I was investigating servo/servo#20474 (comment) turned out to be already be fixed by #428, but there was a few more cases of the same problem.