Skip to content

Rewrite the package to use Symbolics and ReversePropagation #212

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

Merged
merged 19 commits into from
Dec 9, 2024

Conversation

dpsanders
Copy link
Member

@dpsanders dpsanders commented Mar 31, 2024

Update #204 to work with Symbolics 5, IntervalArithmetic 0.22.

@dpsanders dpsanders changed the title Updated rewrite branch Rewrite the package to use Symbolics and ReversePropagation Mar 31, 2024
This was referenced Mar 31, 2024
@schillic
Copy link
Contributor

schillic commented May 2, 2024

Is there a reason to un-support versions below v1.10? That makes this package harder to use downstream when running tests on older versions, so one may have to write version-specific wrapper code.
(Of course, if a v1.10 feature is used, then that is how it is.)

@dpsanders
Copy link
Member Author

The reason is just that I don't know which previous versions will work with this combination. I can change it back.

@dpsanders dpsanders merged commit 6b5a070 into master Dec 9, 2024
20 checks passed
Comment on lines -16 to +18
julia = "1.3"
IntervalArithmetic = "0.22.12"
IntervalContractors = "0.5"
ReversePropagation = "0.3"
Symbolics = "5, 6"
julia = "1"
Copy link
Contributor

Choose a reason for hiding this comment

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

Symbolics v5 already required Julia v1.6, so widening the lower bound from v1.3 to v1.0 seems strange. Maybe you intended to use a higher version?

Copy link
Member Author

Choose a reason for hiding this comment

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

Won't that get resolved automatically?

Copy link
Contributor

Choose a reason for hiding this comment

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

True, just tried it:

(v1.1) pkg> add IntervalConstraintProgramming
[...]
 Installed IntervalConstraintProgramming ─ v0.12.0
[...]

But I still find it misleading when you look at the Project file to know which version you need at least. Then I would rather omit the julia entry completely.

Comment on lines -17 to +14
- '1.3' # oldest Julia version that works
- '1.8' # newest Julia version that works with ModelingToolkit
- '1'
- '1.10'
Copy link
Contributor

Choose a reason for hiding this comment

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

I would not recommend removing the tests on older Julia versions and only testing on v1.10. It is very easy to introduce changes that break old versions unnoticed (I saw it happening many times), particularly because you presumably do not use them for development anymore. If v1.10 is the lowest supported version, that should be reflected in Project.toml (see the other comment).

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm inclined to just set the lower bound as 1.10 since that's the new LTS version, right?

Copy link
Contributor

@schillic schillic Dec 9, 2024

Choose a reason for hiding this comment

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

Totally reasonable.
But note that v1.6-v1.9 would still be installing the current release. So if it broke, that would leave the package in a broken state for these Julia versions. (You could retroactively fix the entry in the registry to raise the Julia version in that case.)

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