Revert custom allocator auditing of MemoryPool tracking in SLTs#22860
Open
avantgardnerio wants to merge 2 commits into
Open
Revert custom allocator auditing of MemoryPool tracking in SLTs#22860avantgardnerio wants to merge 2 commits into
avantgardnerio wants to merge 2 commits into
Conversation
… hazards (apache#22742)" This reverts commit cf01af5.
…vent OOMs (apache#22626)" This reverts commit 488a584.
1 task
|
Thank you for opening this pull request! Reviewer note: cargo-semver-checks reported the current version number is not SemVer-compatible with the changes in this pull request (compared against the base branch). Details |
Contributor
Author
I dislike bots, but this one is spot on! When I added it, I tried to be backwards compatible with a default impl, but if we haven't done a major release in between, I'd say we don't worry about semver as it does not apply. |
Contributor
This was referenced Jun 9, 2026
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
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.
Which issue does this PR close?
No issue, just responding to discussion in #22723
Rationale for this change
Agreed this was an overly strict approach.
What changes are included in this PR?
Reverting previous work
Are these changes tested?
By definition
Are there any user-facing changes?
Contributors won't be held to higher standards in SLTs than in the contributor guide.