You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But wrapping stuff in fs/modified-since? is sometimes a bit verbose. If people could explicitly describe what files are produced by a task, you could automate this:
The :produces will be evaluated so it can be dynamic. If :produces files are newer than what :depends tasks produce we could know that the task does not have to run (this statement needs further investigation though, there must be edge case).
Also we could implement an automatic clean task that will erase all :produces files before running any tasks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In tasks where some tasks are expensive, currently you can use
fs/modified-since
to speed up things:But wrapping stuff in
fs/modified-since?
is sometimes a bit verbose. If people could explicitly describe what files are produced by a task, you could automate this:The
:produces
will be evaluated so it can be dynamic. If:produces
files are newer than what:depends
tasks produce we could know that the task does not have to run (this statement needs further investigation though, there must be edge case).Also we could implement an automatic clean task that will erase all
:produces
files before running any tasks.Beta Was this translation helpful? Give feedback.
All reactions