-
Notifications
You must be signed in to change notification settings - Fork 59
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
Various updates #22
Various updates #22
Conversation
This has the potential to cause breakage, since previous packages that relied on this will now throw a MethodError. However, there doesn't seem to be any way to do this without causing a ton of ambiguities; this can have a cascading effect on other packages that want to check for ambiguities to avoid inadvertently introducing them. A workaround is described in the README.
This ensures the exports work
[bump] Would be nice to get this merged if possible 😊🙏 PS: Minor issue, PPS: I wasn't sure the best way to do this, so I submitted a PR here timholy#1 |
Remove second exported Leaves
Codecov Report
@@ Coverage Diff @@
## master #22 +/- ##
=========================================
Coverage ? 56.29%
=========================================
Files ? 3
Lines ? 302
Branches ? 0
=========================================
Hits ? 170
Misses ? 132
Partials ? 0
Continue to review full report at Codecov.
|
Still passes! If there are no objections, I will merge this in the next few days. |
This contains a grab-bag of mostly-independent commits. The intent of each commit is described in its message. Feel free to accept some but not others. Note the ambiguity test may not run assuming the nightly binaries haven't caught up yet to JuliaLang/julia#30291.