Fabian Meumertzheim
Fabian Meumertzheim
> I am not sure if we should diverge from the official go get behavior. The workflow we recommends in Uber is to add a (potentially dummy) import to the...
Can we shim the library, perhaps by having `GoLibrary` remain an alias of `GoSource` for a while? Otherwise this change could be too breaking to dependents.
Can we just call it `GoInfo` and keep aliases around? That's arguably the canonical name.
I also like the release plan. We should probably fix https://github.com/bazelbuild/rules_go/issues/4062 for that release, I'll look into it tomorrow. The breaking changes David listed are also the three I consider...
> @fmeum shall we merge this? Are we waiting for anything else? Yes and no, just me :-)
Could you post examples of the paths that cause cache misses? I would like to understand why this hasn't come up before.
@pzembrod Could you take a look? This would be a great improvement to Bazel's usability.
I can't reproduce this on Bazel 7.2.1 (and also not on 7.3.1). Could you share a repo with a full reproducer?
Contributions in this area would be very welcome. https://github.com/nelhage/rules_boost appears to be a promising candidate for BCR inclusion.
With all these small inconsistencies between Bazel and the rest of the world, I wonder whether we shouldn't just make Bazel's default toolchain use `clang` for C and `clang++` for...