Fabian Meumertzheim
Fabian Meumertzheim
> > @mtoader do you think we need any improvements to the `bazel mod dump_repo_mapping`? @fmeum offered help if we need any > > There is a bit needed in...
`workspace` works just as any other non-existent repo name: it will result in an error with `--noenable_workspace` (default in Bazel 8) and return a fallback only relevant with WORKSPACE otherwise....
There is no way to warn once, but at least most of the warnings should go away as soon as the user starts migrating individual `resolve` functions.
@tyler-french Could you check https://github.com/bazelbuild/rules_go/pull/4058#issuecomment-2312746844? If this is really an unexpected dependency, I would consider this failure a feature ;-)
This is a nice improvement, including to retained memory. I considered doing this right in the nogo change, but wanted to keep it small. We should wait for the nogo...
Yes, I'll also cut the long due rules_go release!
Yes, feel free to send a PR adding a new entry to that dictionary.
@tyler-french @linzhp This is the minimal change needed to get `go_bazel_test` to pass in the Gazelle repo. The automatic collection of repos from runfiles is problematic with Bzlmod since we...
The providers also have lots of depsets of structs where structs of depsets would be much more memory-efficient. While technically public API, I would say change whatever shows clear benefits.
What's the use case for transitive (rather than direct deps only) recompiles? Does Gazelle ever generate target structures in which this is needed? If the answer is no, we could...