-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
colexec: remove duplication around bazel utility functions #60993
Conversation
pkg/sql/colexecbase/EXECGEN.bzl
Outdated
@@ -71,3 +48,7 @@ def gen_eg_go_rules(): | |||
""", | |||
tools = [":execgen", ":goimports"], | |||
) | |||
|
|||
def rule_name_for(target, visibility=["//visibility:private"]): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this visibility annotation do anything? We're not really using it, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TFTR!
bors r+
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @irfansharif and @rickystewart)
pkg/sql/colexecbase/EXECGEN.bzl, line 52 at r1 (raw file):
Previously, irfansharif (irfan sharif) wrote…
Does this visibility annotation do anything? We're not really using it, no?
I thought it would prohibit from importing this function into another packages, but it seems like it doesn't do anything as you correctly pointed out, so I removed it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wfm
Previously, we had essentially duplicated `.bzl` files in two packages that need to generate code using `execgen`, but this can be avoided by defining a separate `.bzl` file as an extension used in both places. Release note: None
Canceled. |
bors was saying there was a merge conflict, so I rebased and force-pushed (probably that was on a concurrent PR though). bors r+ |
Build succeeded: |
Previously, we had essentially duplicated
.bzl
files in two packagesthat need to generate code using
execgen
, but this can be avoided bydefining a separate
.bzl
file as an extension used in both places.Release note: None