Open lydia-duncan opened 1 month ago
I would advocate for a flag like --print-anon-chpl-settings
, --print-chpl-anon-settings
, --print-chpl-settings-anon
. I think --print-chpl-settings-anonymous
is a really long flag to type, and a standalone --anonymize
flag on chpl
has no meaning without --print-chpl-settings
.
This also matches printchplenv
behavior. I don't know if it is intentional or not (its not documented anywhere), but printchplenv --anon
and printchplenv --anonymize
work the same.
Summary of Feature
Description:
$CHPL_HOME/util/printchplenv
has an anonymize flag that allows printing Chapel settings without details like the path to the user's installation of Chapel. The Chapel compiler itself provides a flag that generates some similar (if more detailed) information,--print-chpl-settings
. Should there be an alternative to this flag or something that prints the same information but is anonymized?Is this a blocking issue with no known work-arounds? No, if a user really wants to sanitize the results, they can do so by hand (it's just annoying)
Code Sample
I'm personally ambivalent about what this should look like, here's some options: