Repository navigation
Callbacks need to handle more use-cases #395
Description
Callbacks currently expect a result to be returned every time. This isn't the case however with things such as git_status_foreac_ext.
Also, the code that is looking for a return value currently doesn't work and we'll need tbranyen/combyne#65 fixed before it works properly.
Additionally we'll need callbacks to handle having their own payloads instead of a universal payload that's sent to each callback. This is stopping the inclusion of many methods that use this pattern.
Activity
johnhaley81 commentedon Feb 11, 2015
This is a blocking issue for #355
tbranyen commentedon Feb 18, 2015
Has this been resolved? Pretty sure I saw multiple payloads in the C++ last I looked.
johnhaley81 commentedon Feb 18, 2015
Not yet. The issue is with callbacks inside of a
classfunction and not inside of astruct.johnhaley81 commentedon Feb 18, 2015
However I was wrong about it being a blocking issue for #355 though.