Ambiguity and warning fixes on 0.4 #63
Merged
Conversation
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
Avoids a new warning.
Collaborator
Author
|
I should add that someday I'll make a much more fundamental change based on JuliaLang/julia#12292, but since that's a big behavior change I might wait until you're ready for a 0.4 fork. |
While these aren't necessary to avoid an ambiguity warnings with base, it turns out they help avoid warnings with other code that uses promotion. I don't _think_ these restrict anything you'd want to allow anyway.
timholy
added a commit
that referenced
this pull request
Aug 3, 2015
Ambiguity and warning fixes on 0.4
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.
Since
!(Dates.Period <: Number), these avoid some long-standing ambiguity warnings.