-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Deprecate negate keyword argument in Dates adjuster API #20213
Conversation
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.
Nice work. I was unaware that you could negate functions via func = !func
.
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.
Looks great! Yes, the composition of !
is a great new feature!
Looks like Nanosoldier didn't get triggered? @nanosoldier |
Network error, had to kick the Nanosoldier: @nanosoldier |
yeah, #17155 hasn't had a news entry added yet |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels |
hopefully won't influence the typical path at all
d236888
to
4feddef
Compare
I took the fact that this needed a rebase after #19920 as an opportunity to push a slight refactoring commit, which should hopefully be exactly equivalent, aside from being more concise. @nanosoldier |
Your benchmark job has completed - no performance regressions were detected. A full report can be found here. cc @jrevels |
This seems very unnecessary, especially now that we have unary
!
for functions. Does anyone use this? We could probably remove theDateFunction
wrapper as well but that's less user-visible so shouldn't matter as much when it happens.Unfortunately keyword arguments are pretty messy to deprecate at the moment.
@nanosoldier
runbenchmarks(ALL, vs = ":master")