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've got a report dk/Prima#144 caused by changes in the stash structure .
I wonder if you could recommend a best course of action about this, in particular how to adapt the code that used to call GvCV(gv_fetchmeth())?
Or, possibly there is a way to keep Prima classes build the old way?
gv_fetchmeth should work transparently by automatically upgrading any non-GV stash entries to full GVs before returning. So it is fine to keep using GvCV(gv_fetchmeth()) . (In particular, I believe the method call machinery can't handle bare CVs and always upgrades to GVs.)
Hello,
I've got a report dk/Prima#144 caused by changes in the stash structure .
I wonder if you could recommend a best course of action about this, in particular how to adapt the code that used to call GvCV(gv_fetchmeth())?
Or, possibly there is a way to keep Prima classes build the old way?
Any insight into this would be much appreciated
cc @mauke
The text was updated successfully, but these errors were encountered: