-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add precompile helper #35
Conversation
Let's hold off on this for a second; I took a quick look myself, and it seems there are quite a few inference problems that can be fixed. Once you eat dessert it's actually harder to eat your vegetables because the caching masks triggers of inference. EDIT: xref #36 |
0fa42ee
to
74dca28
Compare
Codecov Report
@@ Coverage Diff @@
## master #35 +/- ##
===========================================
- Coverage 88.79% 74.43% -14.36%
===========================================
Files 12 13 +1
Lines 562 669 +107
===========================================
- Hits 499 498 -1
- Misses 63 171 +108
Continue to review full report at Codecov.
|
@timholy Small thought.. The timings in the precompile directives file are nice, but frustratingly break git diffs, so it's harder to tell what changes. Any way to have the best of both worlds..? 🤔 |
One point: you could conceivably just use Another one: if you do keep the explicit |
5335bf4
to
8fd0873
Compare
1561dad
to
4825d21
Compare
I'm a bit confused as to why codecov is reporting a reduction here, but should be good to merge @tlnagy |
Oh.. right, codecov is being run on both 1.5 and nightly. So on one the precompiles are being skipped |
This looks good to me. Why are the precompiles only included for 1.6-dev+? Also will I need to rerun this on every release? |
I was being lazy and hadn't checked that they pass for 1.5. Just updated as it works locally for 1.5.3. |
That is one of the down-sides of |
FYI I've not noticed downsides to precompiling for any version after 1.4.2, as long as they are the same precompiles. But before 1.4.2 you can trigger segfaults by precompiling so it's better to be safe. |
I think I would prefer that. I know myself and I'll struggle to remember to rebuild the precompilation signatures regularly. Could you also add |
Great, yeah that simplifies this then. I also added This PR should be squash merged. I didn't rebase squash in case anyone wants to review the intermediate snoop scripts in the future. @timholy looks like FileIO is hitting a precompile directive error on nightly on != ubuntu
|
That will be fixed when JuliaIO/FileIO.jl#295 merges. Should I go ahead and do that or wait longer? From my standpoint it's ready. |
I just commented. Sorry, not had time to give the diff a proper review, but from my perspective I see no reason to not go ahead if you consider it ready |
Can I go ahead and merge this? Little confused by the linked issue. |
It should be safe to merge, but you might want to re-run CI to check? |
If we can merge this, can we get out a new release and merge the FileIO Tiff update? (On my phone, hence the lack of PR links) |
No description provided.