{"push_id":848271613,"size":2,"distinct_size":2,"ref":"refs/heads/59-catch-special-only","head":"d280d385cbf6e21047ffa3936a92868dd38080e7","before":"20d6a3910bd81d865d2b4b4655f1178d83225f96","commits":[{"sha":"2e3ebc105111d4ac1770a55c2afc0ec6998f4322","author":{"email":"d91a8b66ffbf68de959560ff0f2f71d78c01752e@daurnimator.com","name":"daurnimator"},"message":"Only copy event objects onto stack when resuming a cqueues yielded coroutine","distinct":true,"url":"https://api.github.com/repos/daurnimator/cqueues/commits/2e3ebc105111d4ac1770a55c2afc0ec6998f4322"},{"sha":"d280d385cbf6e21047ffa3936a92868dd38080e7","author":{"email":"d91a8b66ffbf68de959560ff0f2f71d78c01752e@daurnimator.com","name":"daurnimator"},"message":"Allow yielding through cqueue_resume => cqueue_process => cqueues_step.\n\nHad to add a \"current thread\" out-arg to cqueue_process to know which thread's stack to push resumed values back onto.\nSeemed a disappointment to not be able to re-use the 'error.thread' field of the callinfo structure.\n\nI had to duplicate a large amount of the cqueue_step function as a continuation;\nthe continuation and the original cqueue_step function should always be kept in sync.","distinct":true,"url":"https://api.github.com/repos/daurnimator/cqueues/commits/d280d385cbf6e21047ffa3936a92868dd38080e7"}]}