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
There's no good reason std::tuple shouldn't be GC-friendly in the same way std::pair is, but I couldn't find a way to get an offset for the element that the compiler would treat as a compile-time constant expression. (The tricks I used for superclasses and fields didn't work.)
I left my latest attempts in, guarded by #ifdef GC_FRIENDLY_TUPLES
The text was updated successfully, but these errors were encountered:
[imported from HPE issue 180]
There's no good reason std::tuple shouldn't be GC-friendly in the same way std::pair is, but I couldn't find a way to get an offset for the element that the compiler would treat as a compile-time constant expression. (The tricks I used for superclasses and fields didn't work.)
I left my latest attempts in, guarded by
#ifdef GC_FRIENDLY_TUPLES
The text was updated successfully, but these errors were encountered: