@gregestren I picked this up since it is relevant for a design I'm working on: I want to build a general-purpose features system for Bazel modules, similar to that of Cargo. Modules can declare configurable features and have appropriate custom Starlark flags generated for them in a repository rule, with a managed default value. But this is only likely to work well if a module can wrap these generated flags in aliases under its own repo, say @rules_cc//cc/config:std aliases @features.rules_cc//:std, which is use_repoed from a module extension.

Hope that motivates this, happy to explain more about the context if you have concerns.

@bazel-io fork 7.2.0