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

Find and suggest fixes for geq/leq with int literals #41

Merged
merged 1 commit into from
Nov 11, 2024
Merged

Conversation

ckaznocha
Copy link
Owner

@ckaznocha ckaznocha commented Nov 11, 2024

closes #38

Also disable because it was as causing CI to fail and I find mnd to be a lot of noise for not much value.

@ckaznocha ckaznocha requested a review from Copilot November 11, 2024 02:48
@ckaznocha ckaznocha self-assigned this Nov 11, 2024

Choose a reason for hiding this comment

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

Copilot reviewed 3 out of 4 changed files in this pull request and generated no suggestions.

Files not reviewed (1)
  • testdata/main.go.golden: Language not supported
Comments skipped due to low confidence (1)

intrange.go:518

  • [nitpick] The function name 'isNumberLit' is not very descriptive. Consider renaming it to 'isIntegerLiteral' to make it clear that it checks for integer literals specifically.
func isNumberLit(exp ast.Expr) bool {
@ckaznocha ckaznocha merged commit dc41474 into main Nov 11, 2024
8 checks passed
@ckaznocha ckaznocha deleted the clif/eq branch November 11, 2024 02:51
@ckaznocha ckaznocha changed the title FInd and suggest fixes for geq/leq with int literals Find and suggest fixes for geq/leq with int literals Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for i <= n
2 participants