Repository navigation
Allow LogExpFunctions 1.x - #327
Merged
adrhill merged 2 commits intoAug 26, 2026
Merged
Conversation
Compat 0.3.28 was a lower bound for loglogistic and friends (PR 195), encoded as [0.3.28, 0.4). LogExpFunctions 1.0 did not remove those names. The package extension loads and its Jacobian and Hessian tests pass on 1.0.1. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Aug 26, 2026
Codecov Report✅ All modified and coverable lines are covered by tests.
Additional details and impacted files@@ Coverage Diff @@
## main #327 +/- ##
===========================================
- Coverage 61.73% 40.22% -21.51%
===========================================
Files 28 28
Lines 1082 1044 -38
===========================================
- Hits 668 420 -248
- Misses 414 624 +210 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Collaborator
|
CI failures look unrelated and will be fixed in a follow-up PR. |
Collaborator
|
See #328. |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
LogExpFunctions = \"0.3.28\"is[0.3.28, 0.4). That floor was set in #195 becauseloglogistic/logitexp/log1mlogistic/logit1mexplanded in LogExpFunctions 0.3.28.LogExpFunctions 1.0.0 (2026-05-28) did not remove those functions. The 1.0 breaking note is a weaker promise on
log2mexp(https://github.com/JuliaStats/LogExpFunctions.jl/releases/tag/v1.0.0). The SCT extension still imports the same names and generates the same 1-to-1 / 2-to-1 tracer overloads.Without this, any package that depends on LogExpFunctions 1 (e.g. SciML NonlinearSolveBase) cannot share an environment with SparseConnectivityTracer.
Local Julia 1.10.11,
Pkg.developthis branch + LogExpFunctions 1.0.1:All 26 names the extension imports (
logistic,logit,xlogx,logaddexp, …) are still defined on 1.0.1.Co-Authored-By: Chris Rackauckas accounts@chrisrackauckas.com
Co-Authored-By: Claude noreply@anthropic.com