Skip to content

[v9] fix: fix major compile time regression due to concrete_getu #3692

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged

Conversation

AayushSabharwal
Copy link
Member

No description provided.

Note that the getter ONLY works for problem-like objects, since it generates an observed
function. It does NOT work for solutions.
"""
Base.@nospecializeinfer function concrete_getu(indp, syms::AbstractVector)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the docstring, this could be typed to avoid mistakenly calling it with other types.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The returned callable has this restriction. I'll have to think about how to handle that case, since it should just work on anything that isn't a solution or a lone parameter object/state vector.

@AayushSabharwal AayushSabharwal changed the title fix: fix major compile time regression due to concrete_getu [v9] fix: fix major compile time regression due to concrete_getu Jun 4, 2025
@ChrisRackauckas ChrisRackauckas merged commit 2ab9c31 into SciML:backport-v9 Jun 4, 2025
14 of 20 checks passed
@AayushSabharwal AayushSabharwal deleted the as/concrete-getu branch June 5, 2025 05:50
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants