Nikolaos Chatzikonstantinou <[email protected]> writes: > On Sun, Oct 5, 2025 at 7:38 PM Tomas Volf <[email protected]> wrote: >> - Tests are not compiled. > > At the time I thought that tests are run-once so I saw no reason to > compile them. I figured that if the tests fail, the programmer will > modify them (and/or the source itself) and re-check, so what is the > point of compiling? On the other hand, I actually ran into a Guile bug > (reported as bug#79479 in bug-guile) that *only* exhibits itself when > the tests are uncompiled. Strange stuff. Other than that, do you have > a good reason to suggest the compilation of the tests?
My main motivation to compile my tests are warnings, in macro heavy code. Guild does not really emit any, unless the macros are actually used. Hence compiling the tests. Auto-compilation could possible work for that as well, but I turn it off, since it is flawed — as implemented in Guile — so I prefer to have the explicit control over the process. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
