-
Notifications
You must be signed in to change notification settings - Fork 15
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 many things reported by JET #152
Conversation
57869b1
to
a8331f1
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #152 +/- ##
==========================================
+ Coverage 73.03% 73.17% +0.13%
==========================================
Files 41 41
Lines 1732 1737 +5
==========================================
+ Hits 1265 1271 +6
+ Misses 467 466 -1 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Lars Göttgens <[email protected]>
Thank you so much! Please send me an email at [email protected] with your name and email and a link to the bounty, so I can set up your reimbursement process with NumFOCUS (it might take a few weeks as we do them in batches and they are still setting everything up for their first batch). |
Resolve #130.
I was able to bring the number of reports down to 33 on julia 1.10. On julia 1.11.0-rc3, there are only 19 left. Many of the remaining things are due to some iterator collection magic in julia base, where I at some point gave up trying to understand it.
What will certainly help with the JET report and type stability in general, but what I see out of scope of this small project:
time
and restrict many of the type signatures for it toUnion{Nothing, TimeType}
. It really does not matter if one uses Float64 or DateTime or whatever for it, but this would help the compiler in some places.If we now tag this function as resumable,
x
will still be referred asUnion{Nothing, Int}
there. For the places that came up I circumvented this by introducing a new variable that just has typeInt
.