-
Notifications
You must be signed in to change notification settings - Fork 246
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
reverse deprecation of find_root, make const #603
reverse deprecation of find_root, make const #603
Conversation
LGTM, thanks for the fix! |
There were several ways of doing this, but I chose one that should be the least intrusive and the easiest to properly deprecate in the future. |
Codecov Report
@@ Coverage Diff @@
## master #603 +/- ##
=========================================
- Coverage 95.04% 94.85% -0.2%
=========================================
Files 33 33
Lines 2825 2835 +10
=========================================
+ Hits 2685 2689 +4
- Misses 140 146 +6
Continue to review full report at Codecov.
|
ping @oxinabox @eulerkochy - this is intended to ameliorate the issues with JuMP. |
Is there a plan to merge and tag this or should we figure out our own workaround in JuMP? JuliaLang/julia#35362 is a good long-term solution but doesn't fix the immediate issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extremely sorry for the delay. LGTM!
@@ -69,6 +69,7 @@ module DataStructures | |||
include("accumulator.jl") | |||
include("classified_collections.jl") | |||
include("disjoint_set.jl") | |||
const find_root = find_root! # remove when deprecating find_root. See deprecations.jl |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just put this in disjoint_sets.jl
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think i would put this in deprecations.jl
Because that is the file I check everytime I am about to make a minor release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one small change reqd.
I think this is the only way forward. What is our exit plan?
I am going to keep out of this statements about how SemVer is supposed to work from this discussion, to find the practical solution. |
(option 5) |
@@ -1,4 +1,4 @@ | |||
@deprecate front(x) first(x) | |||
@deprecate back(x) last(x) | |||
@deprecate top(x) first(x) | |||
@deprecate find_root find_root! # 2020-03-31 | |||
# @deprecate find_root find_root! # 2020-03-31 - reimplement with new minor version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# @deprecate find_root find_root! # 2020-03-31 - reimplement with new minor version | |
# @deprecate find_root find_root! # 2020-03-31 - deprecate in v0.18, or when Julia 1.5 is released. |
Ok, my conclusion is to either: deprecate it in 0.18, or once julia 1.5 is released, which ever comes out first. so I think I am am happy with this. |
closed in #604 |
No description provided.