19793, "bradcray", "Prevent user code from referring to internal module names", "2022-05-11T16:53:09Z"
PR #19788 changes things to prevent internal module names from being automatically available in user code by relying on the new public use behavior introduced in #19306 which is good as internal module names are not meant to be user facing, so having ChapelBase be automatically available is a bit odd. However, it does not prevent user code from writing use ChapelBase; / import ChapelBase; (or similarly for other internal modules). In this issue, I'm proposing that we only resolve internal module names for other internal modules, not for user/package/standard modules.