-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change real to float in cor of a single collection #61
Conversation
As in `cor` we get square root I think it is safe to assume that the result should be floating point. An example of current surprising behavior: ``` julia> cor([im]) true ```
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Though could you add a test to check the new behavior? |
A good point - I have added the tests. They highlight the cases that I think are critical. A check that in all cases we produce what we think should be produced is welcome (I think they are not always intuitive, but I made the PR to be non-breaking in these corner cases except changing the type of |
Codecov Report
@@ Coverage Diff @@
## master #61 +/- ##
========================================
Coverage ? 0.00%
========================================
Files ? 1
Lines ? 381
Branches ? 0
========================================
Hits ? 0
Misses ? 381
Partials ? 0 Continue to review full report at Codecov.
|
I just noticed |
@stevengj You introduced this definition at JuliaLang/julia#13348, replacing |
What do you mean exactly? I have already changed |
Woops, forget it, I was just confused. |
@stevengj Any chance you could find the time to look at this? |
As in
cor
we get square root I think it is safe to assume that the result should be floating point.An example of current surprising behavior: