daviddengcn / gosl Goto Github PK

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.

As I can figure from this post http://golanghome.com/post/331 , the whole script code is executed in a single go main function, is that true?