Hilbish

Author	SHA1	Message	Date
sammyette	b28a2c24c1	refactor!: use userdata where appropriate (#157 ) any interface which has lua side objects that are from go side for its api (namely jobs) they will use userdata instead of always creating a table to represent the object. this might or might not bring lower ram usage since there is now only 1 single reference to an object instead of always creating a table to expose on lua breaking change since methods need to be called with a colon instead of dot	2022-05-28 19:03:44 -04:00
TorchedSammy	d808534da6	perf: use waitgroup instead of loop to wait on timers	2022-05-21 21:58:58 -04:00
TorchedSammy	a4b358fd9c	perf: use struct{} for done channel in timer instead of bool	2022-05-21 21:39:14 -04:00
TorchedSammy	c95ff42dee	feat: add timer pool and api (closes #135 ) adds a map (but lets call it a pool) of all running timers. this makes us able to keep track of all running intervals and timeouts. it also means hilbish can wait for them to be done before exiting (it only waits when non interactive). this introduces the `hilbish.timers` interface, documented by `doc timers`. the `hilbish.interval` and `hilbish.timeout` functions return a timer object now.	2022-04-12 19:31:48 -04:00