You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How do you handle the situation in which you are creating a deferred_ptr to a child node in a member function of a parent node managed by the same deferred_heap and you would like the child to have a deferred_ptr back to the parent?
should there be a way of recovering an already created deferred_ptr using the heap if you have the raw pointer?
The text was updated successfully, but these errors were encountered:
Thanks for this suggestion. For now I'm waiting for feedback and bug reports from actual use of the library, and deferring enhancements and optimizations until then but keeping them in the backlog.
How do you handle the situation in which you are creating a deferred_ptr to a child node in a member function of a parent node managed by the same deferred_heap and you would like the child to have a deferred_ptr back to the parent?
should there be a way of recovering an already created deferred_ptr using the heap if you have the raw pointer?
The text was updated successfully, but these errors were encountered: