3 ms·
> It slows down the development loop because every time you do a build you have to wait for a bunch of unit tests that you don't care about yet. Can't that be
by Alifatisk 2y ago
> It slows down the development loop because every time you do a build you have to wait for a bunch of unit tests that you don't care about yet.
Can't that be an optional thing decided by some compiler flag? I think I remember doing something like that in D.
- kstenerud 2y agoThat's how one would normally do it, and that's what I would expect to see: Build for development, and the compiler only errors out if things are so bad that it's unable emit a binary (for everything else, it emits warnings). Build for release, and it errors out unless EVERYTHING is done right. Unfortunately, ever since golang decided on an autocratic and backwards "there are no warnings, only errors" policy, others have started to sip from the same kool aid jar.