-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fix #15, error with latest StaticArrays due to dot change. #16
Conversation
Thanks! Did you bump the StaticArrays version because this change isn't compatible with older versions? I was going to suggest first restricting StaticArrays at v0.5.1-v0.10, and then applying a change that makes it compatible with v0.11, but it seems that Pkg does not support version ranges yet: JuliaLang/Pkg.jl#843 |
Good point, I guess bumping the StaticArrays lower bound isn't necessary. Pkg does support version ranges, just not spelled that way. The 'correct' thing to do is to retroactively upper bound the StaticArrays version on previous releases, but if we just release a new version with the fix then just doing a I'm going to replace this implementation with a generated function to get the same performance on 1.1 later today. I had trouble getting down to the performance on master without using a generated function. Also, not sure what's going on on Julia 1.0 Travis builds. |
Do you mean like: JuliaLang/Pkg.jl#1232 (comment) , or something else? |
Codecov Report
@@ Coverage Diff @@
## master #16 +/- ##
==========================================
+ Coverage 93.26% 93.42% +0.15%
==========================================
Files 8 8
Lines 208 213 +5
==========================================
+ Hits 194 199 +5
Misses 14 14
Continue to review full report at Codecov.
|
b0d1a39
to
b8fb57a
Compare
OK, switched to the generated function approach, which is fast for both current and future versions of Julia. As for the Travis failures on Julia 1, I can reproduce them locally with Julia 1.0.4. only with code coverage turned on! So I think this is another instance of JuliaLang/julia#30872. |
@rdeits, would you be OK with allowing failures on 1.0? |
Because of #16 (comment).
Went ahead with allowing failures on 1.0. |
@goretkin, I started the process for tagging a new version: JuliaRegistries/General#1483. |
CC: @goretkin.
Microbenchmark results: on Julia 1.1.1:
which at least doesn't allocate, but on latest master:
I think the difference is that an assertion error is being 'outlined' automatically in newer versions. I think this is the cleanest solution going forward, but if you consider this to be too much of a performance bug on 1.1, I can change it.