Introduce managed objects #728
Closed
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
Managed objects derive from `parsec_object_t` and provide a custom release function that can be set by the application. PaRSEC will fall back to calling `free` if no explicit callback is set. Managed objects are tied into the type system because `PARSEC_OBJ_RELEASE` must be able to distinguish them from regular objects. The most common managed object would be `parsec_list_item_t` as that is the basis for all container elements in PaRSEC. Signed-off-by: Joseph Schuchart <[email protected]>
devreal
force-pushed
the
managed-objects
branch
from
9d871db to
001711b
Compare
This was referenced Feb 4, 2025
Contributor
|
We did #731 instead |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Managed objects derive from
parsec_object_tand provide a custom release function that can be set by the application. PaRSEC will fall back to callingfreeif no explicit callback is set. Managed objects are tied into the type system becausePARSEC_OBJ_RELEASEmust be able to distinguish them from regular objects. The most common managed object would beparsec_list_item_tas that is the basis for all container elements in PaRSEC and so we can register a release callback that stashes an object into a container from where it can be retrieved and reused later.This is an alternative to #726 . It's less intrusive but like #726 not ABI backwards compatible but does not change the API.