fix some issues with Vararg#20204
Merged
JeffBezanson merged 2 commits intomasterfrom Jan 26, 2017
Merged
Conversation
- fix #11480, don't use `Type{_} where _<:Vararg` in inference - disallow `Vararg` in type var bounds - disallow `Vararg` as a type parameter in general - move some checks from lower-level functions to apply_type
JeffBezanson
force-pushed
the
jb/vararginffix
branch
from
f252ca5 to
bf2787d
Compare
Member
Author
|
Any thoughts @vtjnash ? |
vtjnash
approved these changes
Jan 25, 2017
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
3 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.
Type{_} where _<:Varargin inferenceVarargin type var bounds (fixes Vararg's cannot be matched with function parameters #19400)Varargas a type parameter in general