Skip to content

Conversation

@noamzaks
Copy link
Contributor

No description provided.

@github-actions
Copy link

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot
Copy link
Member

llvmbot commented May 18, 2025

@llvm/pr-subscribers-mlir-irdl

@llvm/pr-subscribers-mlir

Author: Noam Zaks (noamzaks)

Changes

Full diff: https://github.com/llvm/llvm-project/pull/140460.diff

1 Files Affected:

  • (modified) mlir/include/mlir/Dialect/IRDL/IR/IRDLOps.td (+1-1)
diff --git a/mlir/include/mlir/Dialect/IRDL/IR/IRDLOps.td b/mlir/include/mlir/Dialect/IRDL/IR/IRDLOps.td
index f3bc3497500e7..1508671485785 100644
--- a/mlir/include/mlir/Dialect/IRDL/IR/IRDLOps.td
+++ b/mlir/include/mlir/Dialect/IRDL/IR/IRDLOps.td
@@ -634,7 +634,7 @@ def IRDL_AllOfOp : IRDL_ConstraintOp<"all_of",
     ```
 
     The above program defines a type `complex` inside the dialect `cmath` that
-    can has one parameter that must be 32-bit long and a float (in other
+    can have one parameter that must be 32-bit long and a float (in other
     words, that must be `f32`).
   }];
 

@math-fehr math-fehr self-requested a review May 19, 2025 01:45
Copy link
Contributor

@math-fehr math-fehr left a comment

Choose a reason for hiding this comment

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

Thanks for pointing this out!
I left a comment because I think we should word it differently, tell me what you think!


The above program defines a type `complex` inside the dialect `cmath` that
can has one parameter that must be 32-bit long and a float (in other
can have one parameter that must be 32-bit long and a float (in other
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
can have one parameter that must be 32-bit long and a float (in other
has one parameter that must be 32-bit long and a float (in other

Actually, I think has would be better than can have here, because the parameter is required. Otherwise, readers might think that it is optional. What do you think?

Copy link
Contributor Author

@noamzaks noamzaks May 19, 2025

Choose a reason for hiding this comment

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

Sure, I chose "can have" because it is used in line 600 as well, so I'll change both (since it's not optional)

Copy link
Contributor

@math-fehr math-fehr left a comment

Choose a reason for hiding this comment

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

Even better, thanks for fixing it elsewhere too!

@math-fehr math-fehr merged commit d0ee358 into llvm:main May 19, 2025
7 checks passed
@github-actions
Copy link

@noamzaks Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants