Having a library like libfileis(3) in the src/ directory is an exception to the "one file, one program" unofficial rule every other file follows. libfileis isn't necessary for scrut(1) and was removed from scrut because it wasn't a great solution for scrut in particular, stat(3)ing each specified file for every condition the file had to pass (like: for file in args { for test in tests { stat(3) file, check struct stat buffer for test } }).
libfileis' greatest utility to me as the writer is as a reference for how to check all of its included conditions, not as code to actually be run.
Having a library like libfileis(3) in the src/ directory is an exception to the "one file, one program" unofficial rule every other file follows. libfileis isn't necessary for scrut(1) and was removed from scrut because it wasn't a great solution for scrut in particular, stat(3)ing each specified file for every condition the file had to pass (like: `for file in args { for test in tests { stat(3) file, check struct stat buffer for test } }`).
libfileis' greatest utility to me as the writer is as a reference for how to check all of its included conditions, not as code to actually be run.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Having a library like libfileis(3) in the src/ directory is an exception to the "one file, one program" unofficial rule every other file follows. libfileis isn't necessary for scrut(1) and was removed from scrut because it wasn't a great solution for scrut in particular, stat(3)ing each specified file for every condition the file had to pass (like:
for file in args { for test in tests { stat(3) file, check struct stat buffer for test } }).libfileis' greatest utility to me as the writer is as a reference for how to check all of its included conditions, not as code to actually be run.
Pull request closed