feature request: caching

[radiofreejohn]

It might make sense to maintain some small cache of recently run scripts. You could do this by generating a hash of the file contents and using that when you generate the file name to use, if the file already exists, execute it and leave the binary, if not, generate it.

You'd have to decide how many recent files to keep and make sure old entries are cleaned up so that binaries don't end up taking up a lot of space, but you could touch the files and purge least recently used files after some threshold size is reached.

This would be useful for scripts that are run very frequently I think, which is probably a common use case.

[daviddengcn]

Thanks for the interest in gosl project. This may be a good feature for some case, but I personally don't have a real usecase that runs very frequently yet. Can you help me think of this?

[radiofreejohn]

Most of my bash scripts end up as cron jobs. I guess if they are to be reused a lot you can just build them normally. Is there an easy way to get a binary from a gosl script if you end up wanting to use it repeatedly?

[tompao]

For maintaining a cache, you might find useful to look at gorun:https://github.com/erning/gorun/blob/master/README.md

[daviddengcn]

@radiofreejohn, I can add some options for gosl to export the source or compiled binary.

[daviddengcn]

@tompao, thanks! That'll help!

[radiofreejohn]

sounds good, thanks!