Sergio Pastor Pérez <[email protected]> writes: > Hello, > > Zacchaeus <[email protected]> writes: > >> Hi Guix, >> >> >> Re my previous email below, does anyone know a solution to large >> define-cofigurations? Can they be thunk'd or something so they are only >> slow if you use them?
I guess you can take a look at make-home-mpv-configuration and do something similar? I did not follow this thread in detail, so maybe it is not applicable to your use case. > > Why would they be slow? It shouldn't be a problem, thunking will only > delay the problem until you do the serialization, which will still > happen when doing the build of the system; you would only gain worse > error detection. This is a known issue, you can check https://issues.guix.gnu.org/74748 for my bug report and Ludovic's investigation. > >> Is there some other solution to configure Guix >> services for programs with a lot of fields? I'd really like a >> mainlineable solution for email[0]. > > If you mean that the module takes longer to compile, that's fine, > modules with more services will have the same problem. Yes, you service > is quite big, but not as big as `rust-crates`, so the module shouldn't > be in the ballpark where we need to be concerned about the size. Users > will get the modules compiled during the `guix pull`, so it shouldn't be > a concern when deploying the system. > > Am I missing something? It is really bad DX when experimenting with a configuration in REPL takes 30 seconds to construct the object like it did in my case. Have a nice day, Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
