@item check that @file{stdout} and @file{$3} are not written simultaneously
@item check that generated target was not modified "externally" outside
the redo, preventing its overwriting, but continuing the build
+ (optionally can stop)
@end itemize
+@item recursive, indented and serialized logs display ability, with
+ priority to the depth and bad return codes, like in @command{apenwarr/redo},
+ thanks to @url{https://apenwarr.ca/log/20181106, apenwarr's article}
+@item all environment variables, working directory, command line
+ arguments, start/finish times, duration, participated PIDs, return
+ codes can be saved for later investigation
@item targets, dependency information and their directories are explicitly
synced (can be disabled, should work faster)
-@item file's change is detected by comparing its size, @code{ctime} (if
- @env{REDO_INODE_NO_TRUST} environment variable is not set) and
- @url{https://github.com/BLAKE3-team/BLAKE3, BLAKE3} hash
+@item file's change is detected by comparing its size, and
+ @url{https://github.com/BLAKE3-team/BLAKE3, BLAKE3} hash. Also as an
+ optimization, by default if file's @code{ctime} is same, then hash
+ check is skipped. Optionally you can disable that behaviour, or even
+ enable trust to file's @code{mtime}
@item files creation is @code{umask}-friendly (unlike @code{mkstemp()}
used in @command{redo-c})
@item parallel build with jobs limit, optionally in infinite mode