Carbon toolchain environment drift without pinned dependencies
Developing with Carbon currently requires building the toolchain from source using Bazel, Clang, and Python. Because the project is in an experimental phase, the documentation lacks pinned dependency lockfiles, release tags, or container digests to ensure a repeatable development environment. Without a mechanism to lock the toolchain versions or standard lib
bazel