Currently a MODULE.bazel file might look like this:
module(
name = "foo",
version = "2.0",
toolchains_to_register = ["@toolchain_repo//:toolchain"],
)
ext = use_extension("//:extensions.bzl", "ext")
ext.some_tag()
use_repo(ext, "toolchain_repo")
The toolchains_to_register values way precede the definition of the used repo (toolchain_repo). If we had a register_toolchains API, we could request to register the toolchain after the use_repo call instead, which is easier to read and maintain.
This change should have absolutely no impact on the behavior of toolchain/execution platform registration.
Currently a MODULE.bazel file might look like this:
The
toolchains_to_registervalues way precede the definition of the used repo (toolchain_repo). If we had aregister_toolchainsAPI, we could request to register the toolchain after theuse_repocall instead, which is easier to read and maintain.This change should have absolutely no impact on the behavior of toolchain/execution platform registration.