docshelp wanted
Métriques du dépôt
- Stars
- (48 709 stars)
- Métriques de merge PR
- (Merge moyen 23j 11h) (145 PRs mergées en 30 j)
Description
As far as I can tell, there's currently no built-in way to cache a precompiled module if it's not part of a package. There's two problems here:
- This isn't made sufficiently clear by the documentation on module precompilation. In fact, that section of the docs says you can cache arbitrary precompiled modules by simply calling
Base.compilecache. This is clearly not the case sinceBase.compilecachetakes aPkgIdas its argument. - For use-cases involving distributing a single script with relatively long compilation-time and short run-time, this leaves a lot of performance on the table. For me a couple times its made the difference between whether or not Julia was a viable language for the problem.
So is there any way to either:
- Cache precompiled arbitrary modules using the current infrastructure in
~/.julia/compiledor - Automatically cache modules not part of packages in the same directory as the file(s) with the module or
- Provide a documented way of creating
.jifiles programmatically for a given module from within julia code and also loading said.jifiles if they already exist.
The documentation on module precompilation should also be fixed, but I'm not confident enough in my understanding of the relation between Base and Pkg to do so myself.