Plans for v0.14 update #84
Replies: 3 comments 1 reply
-
@JoshuaLampert let me know if there's anything I'm missing above or that you'd like to implement prior to |
Beta Was this translation helpful? Give feedback.
-
I'm very happy with how the internal structure evolved with this breaking release. The implementation looks pretty clean to me. We are also at 99.25 % code coverage now, which is pretty cool 🥳 So v0.14 is good to go from my point of view. I don't have any other breaking changes in mind. |
Beta Was this translation helpful? Give feedback.
-
Thanks, and thanks again for all of your inputs, feedback, and brainstorming! Between the last non-breaking refactor PR that got merged into v0.13 and all of these changes, I think the codebase here has been massively improved in quality. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Breaking Changes
IntegrationAlgorithm
toIntegrationRule
. Consolidate terminology around integration rules (versus "algorithms", "settings", etc).derivative
andunitdirection
functions. Allderivative
functionality was merged intojacobian
.derivative
andunitdirection
from exports #88FP
to a keyword argument #91FP
from an optional argument to a keyword argument.FP
to a keyword argument #91Non-Breaking Changes
Development/Testing Infrastructure
specialized
source file explaining why each of theseGeometry
s requires specialized methods rather than using the generalized ones?@testset
forBezierCurve
with analytic solutions.differential
andjacobian
for Bezier curve integrals #92compat
entries.Beta Was this translation helpful? Give feedback.
All reactions