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

Bump DataStructures version #2315

Merged
merged 2 commits into from
Aug 21, 2020
Merged

Bump DataStructures version #2315

merged 2 commits into from
Aug 21, 2020

Conversation

jd-lara
Copy link
Contributor

@jd-lara jd-lara commented Aug 20, 2020

No description provided.

@codecov
Copy link

codecov bot commented Aug 20, 2020

Codecov Report

Merging #2315 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2315   +/-   ##
=======================================
  Coverage   91.32%   91.32%           
=======================================
  Files          42       42           
  Lines        4255     4255           
=======================================
  Hits         3886     3886           
  Misses        369      369           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6e329c8...aad63ab. Read the comment docs.

@dourouc05
Copy link
Contributor

As nothing changed in the code, it would be best to allow both 0.17 and 0.18, I suppose. (As long as the tests pass with both versions.)

@jd-lara
Copy link
Contributor Author

jd-lara commented Aug 20, 2020

I am not sure what the rules are for the JuMP community but there are function name upgrades between versions that aren't compatible. For example, the function top changed to overload Base.first.

This in my understanding is non backwards compatible between versions.

@dourouc05
Copy link
Contributor

As long as JuMP doesn't use these names (otherwise, your PR would be much longer), then this change is not relevant: this update might break compatibility in some cases, but not the interesting ones. As long as JuMP doesn't require any change, I don't think it's good behaviour to force users of JuMP to update: in some cases, they might even be unable to do so due to other dependencies… I suppose this is the understanding behind the large compatibility range for ForwardDiff.jl (JuMP announces compatibility for versions 0.5 to 0.10, i.e. more than three years of development with compatibility breakages).

@jd-lara
Copy link
Contributor Author

jd-lara commented Aug 20, 2020

ok, I have added "0.17" to the compat.

@mlubin
Copy link
Member

mlubin commented Aug 20, 2020 via email

@mlubin mlubin merged commit dd28744 into jump-dev:master Aug 21, 2020
@andreasnoack
Copy link

Since DataStructures is so wide used, it would be helpful if you could make a patch release that allows for version 0.18.

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

Successfully merging this pull request may close these issues.

4 participants