-
Notifications
You must be signed in to change notification settings - Fork 545
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
0.5.x: Remove everything deprecated #1394
Conversation
b0d3db4
to
2e6f76c
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## 0.5.x #1394 +/- ##
==========================================
+ Coverage 93.51% 94.16% +0.65%
==========================================
Files 34 34
Lines 17018 16824 -194
==========================================
- Hits 15914 15842 -72
+ Misses 1104 982 -122 ☔ View full report in Codecov by Sentry. |
de6a518
to
e9bba9c
Compare
We may want to backport the first two commits (documentation and test fixes) to the 0.4 branch. |
That sounds good to me. |
Yes, I think we should do that in the same commit. |
8acce1a
to
ad308cc
Compare
Because the renames are touching so many lines I split them out in separate commits. Easy to squash if you do prefer them combined though. I don't really want to make a lot of changes to the file for |
ad308cc
to
69a665f
Compare
Remove everything that is deprecated on the 0.5 branch.
I was wondering if it was better to rename the replacement methods at the same time as removing the deprecated methods, or to leave that for another PR. I.e. renaming things like
FixedOffset::east_opt
toFixedOffset::east
.