Add AutoDespecialize parameter policy - #1514
Merged
ChrisRackauckas merged 1 commit intoAug 11, 2026
Merged
Conversation
Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
ChrisRackauckas
marked this pull request as ready for review
August 11, 2026 08:23
This was referenced Aug 11, 2026
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.
What changed
Adds
AutoDespecializeas a specialization policy distinct from both the unchangedAutoSpecializepolicy and the constrainedAutoRespecializepolicy. Supporting solvers can use it to place arbitrary parameter objects behind the existingDespecializedParametersdynamic function barrier, while transformations can opt out throughunwrap_parameters.The new public marker is documented and included in the specialization preference allowlist. This is a minor public API addition, so the package version advances to 3.46.0.
Verification
Before this commit, the public marker discriminator failed:
After this commit:
The exact docs build on current
masterreachesCheckDocumentand then fails only on the 16 pre-existingProblem_TraitsHTTP 403 links. With the focused existing fix from #1485 stacked locally, the same command completes doctests, cross-references, rendering, and link checking with exit 0:Runic 1.7,
typosover the changed files, andgit diff --checkall exit 0.Not verified here
Solver-side automatic wrapping and precompilation are intentionally separate changes in DiffEqBase/OrdinaryDiffEq. ModelingToolkit's default selection and parameter-interface forwarding are also separate so each ownership boundary remains independently reviewable.
Draft: ignore until reviewed by @ChrisRackauckas.
Links