Revert custom allocator auditing of MemoryPool tracking in SLTs#22860
Conversation
… hazards (apache#22742)" This reverts commit cf01af5.
…vent OOMs (apache#22626)" This reverts commit 488a584.
|
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 |
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. |
|
Thanks again @avantgardnerio |
…he#22860) ## Which issue does this PR close? No issue, just responding to discussion in apache#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.
I'm happy that you find it useful, it provide 2 benefits:
|
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.