Skip to content
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

add_heir_dialect_library build macro for bazel #1236

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

ZenithalHourlyRate
Copy link
Collaborator

Related to #1045, similar to #1055 and see also #1235 where the verbose gentbl_cc_library is error-prone.

This PR demos the usability of such macro for LWE/Openfhe dialect. If such change is favored, further PR will update other BUILD file and the template generator.

Copy link
Collaborator

@j2kun j2kun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@j2kun j2kun added the pull_ready Indicates whether a PR is ready to pull. The copybara worker will import for internal testing label Jan 6, 2025
@j2kun
Copy link
Collaborator

j2kun commented Jan 7, 2025

So I am patching this internally to fix the conflicts, and I will merge it, but I have a request to make for any followups to this: the generated target name and the file being read should always be provided as input to the macro. This will require more typing, but will be more readable, otherwise when looking at a target with a dependency like dialect_inc_gen, you will not easily be able to tell where it came from (it fails the grep test), and if you have a filename you will not easily be able to see which target depends on it.

Filed #1242 to remind us

@copybara-service copybara-service bot merged commit 9c08a43 into google:main Jan 7, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pull_ready Indicates whether a PR is ready to pull. The copybara worker will import for internal testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants