17791, "lydia-duncan", "Deprecation and configs", "2021-05-20T19:51:57Z"
While it seems pretty easy to add a warning when a deprecated config var, const or param is referenced in Chapel code, I think the behavior when it is referenced via the compilation or execution command is a little more up in the air so wanted to double check before implementing my instincts.
For example, say you have the following:
deprecated "don't use x, use y" config var x: bool = false;
config var y: bool = false;
proc main() {
writeln(x);
writeln(y);
}
and you compile it with chpl -sx=true foo.chpl. Should the act of using the compilation flag trigger a separate warning message from the writeln in the code? What about if it was set at execution time, e.g. ./foo --x=true?
My instinct says the flag use should trigger its own warning message.