-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Implementation of var(v::Range) is not type-stable #22773
Comments
andreasnoack
added a commit
that referenced
this issue
Jul 12, 2017
Looks like this line should be l < 2 && return momenttype(eltype(v))(NaN) ( |
Might be a good use for return type annotation? |
andreasnoack
added a commit
that referenced
this issue
Jul 17, 2017
andreasnoack
added a commit
that referenced
this issue
Jul 17, 2017
andreasnoack
added a commit
that referenced
this issue
Jul 17, 2017
jeffwong
pushed a commit
to jeffwong/julia
that referenced
this issue
Jul 24, 2017
ararslan
pushed a commit
that referenced
this issue
Sep 11, 2017
ararslan
pushed a commit
that referenced
this issue
Sep 13, 2017
vtjnash
pushed a commit
that referenced
this issue
Sep 14, 2017
ararslan
pushed a commit
that referenced
this issue
Sep 15, 2017
ararslan
pushed a commit
that referenced
this issue
Sep 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Return type of, e.g.,
var(0f0:1f0:10f0)
isUnion{Float32, Float64}
, due to conditional return ofNaN
in the implementation.Example:
var(v::Range{T})
should probably returnreal(momenttype(T))
in all cases, likevar(A::AbstractArray{T})
does.May also affect implementation of similar functions.
The text was updated successfully, but these errors were encountered: