Adriano Fantini

Thank you for your quick reply. That helps. I'll try to see how to approach this in an efficient way. Feel free to close or to keep this open to...

A possible solution would be to run an inner generator when the function is run the first time, and store the output in a global variable. Something like this: ```lua...

A cleaner version of the previous approach: ```lua local function generateFunc(code, name) --[[ When using Effil, functions with custom environments often cannot be serialised. See: https://github.com/effil/effil/issues/169 For this reason, we...

Thank you. So you confirm there is no way to work around this limitation, other than the hack I posted above? Maybe Effil could avoid seralising global built-in Lua functions?

Some more testing, I got it to work. It appears the problem was twofold: 1. I think cannot assign a `runner` to a serialised effil.table. Only the `thread` object can...

I see, thank you. But then why does `local myprint = function(...) print(...) end` work? Is it enough to wrap each C function in a lua wrapper to be able...

Thank you for the reply, I see what you mean. Looking forward to the MR with mutex functionality.

> I've never used the `PCICt` object. Can you please provide a data frame example that contains a column of `PCICt` and describe what interval you expect to see from...

> Do you expect the following example gives you an hour interval? `PCICt` AFAICT defines some arithmetic function so that adding `3600` seconds is always an hour (no matter the...

> You don't need to know deeply about `tsibble`, but more about how to calculate the interval from `PCICt`. > > I suppose I don't have time to implement this...