Skip to content
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: avoid ConstructionBase.setproperties ambiguity #634

Merged

Conversation

AayushSabharwal
Copy link
Contributor

@AayushSabharwal AayushSabharwal commented Aug 19, 2024

Fixes this ambiguity. The ConstructionBase docs explicitly recommend adding a method to setproperties (setproperties_object is undocumented internals) and type-annotating patch::NamedTuple.

@devmotion
Copy link
Contributor

This change also broke old SymbolicUtils versions such as eg. 1.5.1 or 1.7.0 (which I have to keep using for now due to compatibility with MTK v8: #595). Can we backport this fix to older versions?

@ChrisRackauckas
Copy link
Member

Yes we can backport. Just to v2?

@ChrisRackauckas ChrisRackauckas merged commit c062be7 into JuliaSymbolics:master Aug 19, 2024
7 of 10 checks passed
@devmotion
Copy link
Contributor

Backporting to v1 is necessary for MTK 8.

ChrisRackauckas added a commit that referenced this pull request Aug 19, 2024
fix: avoid `ConstructionBase.setproperties` ambiguity
ChrisRackauckas added a commit that referenced this pull request Aug 19, 2024
fix: avoid `ConstructionBase.setproperties` ambiguity
ChrisRackauckas added a commit that referenced this pull request Aug 19, 2024
fix: avoid `ConstructionBase.setproperties` ambiguity
@ChrisRackauckas
Copy link
Member

Backported all the way to v0.19

@AayushSabharwal AayushSabharwal deleted the as/fix-setproperties branch August 19, 2024 11:43
@devmotion
Copy link
Contributor

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants