Hi Hugo, Hugo Buddelmeijer via "Development of GNU Guix and the GNU System distribution." <[email protected]> writes:
> On 8/6/26 13:53, [email protected] wrote: >> From my experience the guix commands given after `pre-inst-env` are >> doing the byte code compilation when necessary, but they are not saving >> the byte code compiled .go files next to the .scm files > > Can we make it such that the compiled code is always stored? It seems > silly to discard it. I once thought the same, but with experience realise that the Guile compiler would need to be smarter to make this a great experience. You may have noticed for example that when we change a record it's necessary to manually invalidate the .go files (make clean-go) and rebuild? This kind of issue would also happen with 'on-the-fly' byte-compiled files, but you'd then have to hunt the problematic .go files from under a less discoverable location like ~/.cache/guile/ccache/3.0-LE-8-4.7. I believe this may be the reason that '--no-auto-compile' is used in Guix and other Guile projects. -- Thanks, Maxim
