delete old deprecations #13352
Merged
delete old deprecations #13352
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erik-krogh
force-pushed
the
once-again-deps-not-py-cpp
branch
from
616e540 to
ac9ede4
Compare
Yeah, I think it's fine to not have a change note for these. |
asgerf
approved these changes
Jun 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not Python or C++ (except for files that are synchronized).
Those have complications, so they get their own PRs after this one has been merged.
Notes about change-notes:
C++: All changes seems to be in
internal/orimplementation/folders, so I don't think those need change-notes?All: For most languages there were too many deleted classes/classes to reasonably list. So I went for a general note about using PascalCase instead of UPPERCASE.