Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should has_*() functions be user-facing? #34

Open
beanumber opened this issue Dec 11, 2018 · 1 comment
Open

Should has_*() functions be user-facing? #34

beanumber opened this issue Dec 11, 2018 · 1 comment

Comments

@beanumber
Copy link
Collaborator

If a has_*() function, for example, has_only_portable_paths() requires compilation, then what is the best way to check if the project needs to be re-compiled?

In check(), we are going to run a bunch of these, so we compile once first, then do the checks. But if you just want to run one of these functions as a one-off, how is it supposed to know whether the log file accurately captures what happens during compilation? If we allow each function to trigger proj_render(), then this will be horribly inefficient.

@beanumber
Copy link
Collaborator Author

write .fertile file and record timestamp, then compare timestamp to file dates when function is called.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant