At times, it may be advantageous for a solution to a challenge to make certain assumptions about, for example, the directory from which it is run. For example, a bash script that compiles and runs a file with
gcc can reduce
if it can safely assume that no other files in the present working directory have a name that begins with
Should this be allowed? What about assumptions about the file name of the code being run? We already have a policy that adds the length of the file name to the score if it has to have a certain name (informal? I can't find a definitive statement of this policy), but what if the file name simply can't be a certain string (for example, the bash script above would have to have a name that doesn't start with
Another interesting conundrum is tricks like
/d*/u*m instead of
/dev/urandom. On my system,
/dev/urandom is the only file that matches the glob, but this may not be the case on others.
How should these cases be handled?
(note that my self-answers are intended as proposals and not declarations; treat them in the same manner as you would if they were posted by any other user.)