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
I have a need for a managed-lifetime struct with recursive references, so I was hoping to be able to use the M-SHARED container to implement this but it appears that M-SHARED requires a fully-defined struct due to its optimization using the "combine_s" struct.
It could be good to include this detail in the README interface documentation. If there could be a way to avoid the use of that combine mechanism for forward declared structs that would be helpful in the longer-term.
The text was updated successfully, but these errors were encountered:
The definition of the combine_s structure can easily be deactivated if the INIT and EMPLACE_TYPE operators are disabled (This will prevent the definition of _init_new and the _emplace functions). Is such change sufficient for you?
I have a need for a managed-lifetime struct with recursive references, so I was hoping to be able to use the M-SHARED container to implement this but it appears that M-SHARED requires a fully-defined struct due to its optimization using the "combine_s" struct.
It could be good to include this detail in the README interface documentation. If there could be a way to avoid the use of that combine mechanism for forward declared structs that would be helpful in the longer-term.
The text was updated successfully, but these errors were encountered: