diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-07-22 23:36:19 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-07-22 23:36:19 -0700 |
commit | 60e11efcb042cb9cfb3fc50d8d7e36d74020b6ae (patch) | |
tree | 939aba1c2493874df2af1fbf09a663803b048e32 /lambda-to-mu.mu | |
parent | d8f7ec8ec9251e4f4aef179e83d291c7518e984e (diff) | |
download | mu-60e11efcb042cb9cfb3fc50d8d7e36d74020b6ae.tar.gz |
3137
Complicated logic to not run core tests. I only want to disable core tests if: a) I'm changing CFLAGS on the commandline (usually to disable optimizations, causing tests to run slower in a debug cycle) b) I'm not printing a help message (either with just 'mu' or 'mu --help') c) I'm loading other files besides just the core. Under these circumstances I only want to run tests in the files explicitly loaded at the commandline. This is all pretty hairy, in spite of my attempts to document it in four different places. I might end up taking it all out the first time I need to run core tests under all these conditions.
Diffstat (limited to 'lambda-to-mu.mu')
0 files changed, 0 insertions, 0 deletions