Uh oh!
There was an error while loading. Please reload this page.
Conversation
ChrisRackauckas
commented
Aug 27, 2020
I'd say we do #419 and #463, which I don't think are actually breaking changes, but can be considered breaking changes, and we can call that v1.0. Then, once it's v1.0, I'd say we can document the Dual number interface, #379 because I'd hope no one would ever change that. I'd like to get @KristofferC and @jrevels 's input though. But I think it's pretty safe to say, ForwardDiff works and if you want a very different AD then make a new package. |
oxinabox
commented
Aug 27, 2020
I agree with those 2 PRs. |
Codecov Report
@@ Coverage Diff @@## master #467 +/- ##
=======================================
Coverage 87.31% 87.31% =======================================
Files 10 10 Lines 757 757 =======================================
Hits 661 661 Misses 96 96 Continue to review full report at Codecov.
|
fredrikekre
commented
Aug 27, 2020
Please don't make a non-breaking 1.0.0 release. |
oxinabox
commented
Aug 28, 2020
Its an unfortunate concisquence of julia's semver extension that 1.0.0 is always considered breaking. But in this case I am kind of happy to have it considered breaking because #463 is borderline breaking. |
cossio
commented
Sep 12, 2021
Something holding this? |
KristofferC
commented
Sep 12, 2021
If someone wants to do this they need to make a corresponding change to the registry that allows ForwardDiff 1.0 for those packages that are currently claiming compatibility with ForwardDiff 0.10. |
oscardssmith
commented
Sep 2, 2022
1.0 has already been tagged. |
oscardssmith
commented
Sep 2, 2022
I don't know how to read. |
Noone wants to change FowardDIff.
It is stable.
Even if one does want to change ForwardDiff, noone wants to change the API in a breaking way.