New Issue: What should we call the user-facing replacements for common CHPL_* checks?

Notifications Issues
1

19188, "bradcray", "What should we call the user-facing replacements for common CHPL_* checks?", "2022-02-04T21:42:10Z"

In reviewing the ChapelEnv.chpl module, soon to become the ChplConfig.chpl module, we decided to add support for common queries using a nicely named user-facing routine rather than having users compare against CHPL_* environment variables. Based on the experience of https://github.com/chapel-lang/chapel/pull/19162, the most common queries are:

  • CHPL_COMM=="none" (or !=): "Is this program being compiled for a single locale only, or for multiple locales?"
  • CHPL_COMM=="ugni" or CHPL_NETWORK_ATOMICS!="none": "Is this program being compiled for a configuration that supports network atomics?"

This issue asks for proposals as to what we should call such queries. So far, I've only thought of ideas I don't like, so I'm not seeding the conversation with any proposals.