Fabian Meumertzheim

@c-mita We are also running into this so I would be interested in moving it forward in some way. Do you think this could be worked around by having separate...

@keith Do you know of a workaround that applies to earlier versions of Bazel? A recent regression in Bazel on Windows prevents me from using https://github.com/bazelbuild/bazel/releases/tag/6.0.0-pre.20220922.1.

In my experience, it's usually easier to gain consensus for a PR than on issue comments. Given that these questions probably don't warrant a design doc yet, I will look...

@UebelAndre I just submitted https://github.com/bazelbuild/bazel/pull/16430, which implements `arguments` but does not yet expose it to Starlark. This should address your original request while evading potentially difficult questions around what the...

> I'm not sure what you mean by this. Looking at the PR it seems like you added the ability to set `arguments` in starlark rules. Are you saying I'm...

@sgowroji This has been resolved by #15006.

@kshyanashree As this is naturally included in Bazel 6, you can remove the "potential-release-blocker" label.

@rstoica Great to see somebody else interested in this. > One way to support Bluetooth "out-of-the-box" is via HID over Bluetooth Profile support. I don't know what @jcjones had in...

Being able to select between Go SDK versions sounds very useful. Thanks for the suggestion and willingness to implement it! I would prefer a slightly more general approach. What do ...

I'm thinking of a rule that allows the following: ```starlark go_binary( name = "foo", ... ) go_cross( name = "special_foo", target = "foo", platform = "//:my_custom_platform", sdk_version = "1.17", )...