Skip to content

WhoAllocated<T> doesn't need to be generic over any T#901

Merged
eeeebbbbrrrr merged 2 commits into
developfrom
whoallocated-no-T
Dec 5, 2022
Merged

WhoAllocated<T> doesn't need to be generic over any T#901
eeeebbbbrrrr merged 2 commits into
developfrom
whoallocated-no-T

Conversation

@eeeebbbbrrrr

Copy link
Copy Markdown
Contributor

... so this changes it to just WhoAllocated.

I wanted to put it up now as I'm going to be working on some stuff that this will make better.

@eeeebbbbrrrr eeeebbbbrrrr mentioned this pull request Nov 30, 2022
@eeeebbbbrrrr eeeebbbbrrrr merged commit 35c28b8 into develop Dec 5, 2022
yrashk pushed a commit to yrashk/pgx that referenced this pull request Dec 6, 2022
…oundation#901)

* `WhoAllocated<T>` doesn't need to be generic over any `T`, so this changes it to just `WhoAllocated`.

* rename the `WhoAllocated::free` function to `WhoAllocated::maybe_free` and add some doccomments.
@eeeebbbbrrrr eeeebbbbrrrr deleted the whoallocated-no-T branch June 20, 2023 18:01
usamoi pushed a commit to tensorchord/pgrx that referenced this pull request Mar 6, 2025
…oundation#901)

* `WhoAllocated<T>` doesn't need to be generic over any `T`, so this changes it to just `WhoAllocated`.

* rename the `WhoAllocated::free` function to `WhoAllocated::maybe_free` and add some doccomments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants