Skip to content

Conversation

@resyntax-ci
Copy link
Contributor

@resyntax-ci resyntax-ci bot commented Nov 7, 2025

Resyntax fixed 20 issues in 10 files.

  • Fixed 6 occurrences of match-let-to-match-define
  • Fixed 2 occurrences of error-to-raise-arguments-error
  • Fixed 2 occurrences of let-to-define
  • Fixed 2 occurrences of define-let-to-multi-define
  • Fixed 2 occurrences of if-else-false-to-and
  • Fixed 1 occurrence of if-let-to-cond
  • Fixed 1 occurrence of begin0-begin-extraction
  • Fixed 1 occurrence of format-string-to-format-symbol
  • Fixed 1 occurrence of nested-if-to-cond
  • Fixed 1 occurrence of inverted-when
  • Fixed 1 occurrence of format-identity

resyntax-ci bot added 12 commits November 7, 2025 01:07
Internal definitions are recommended instead of `let` expressions, to reduce nesting.
This `if`-`else` chain can be converted to a `cond` expression.
This `let` expression can be pulled up into multiple `define` expressions.
`cond` with internal definitions is preferred over `if` with `let`, to reduce nesting
This `if` expression can be refactored to an equivalent expression using `and`.
Internal definitions are recommended instead of `match-let` expressions with a single binding, to reduce nesting.
The `begin` form inside this `begin0` form can be extracted into the surrounding definition context.
This negated `when` expression can be replaced by an `unless` expression.
Use `raise-arguments-error` instead of `error` for better error messages that follow Racket conventions.
This `format` expression can be simplified to an equivalent `format-symbol` expression.
This use of `format` does nothing.
Internal definitions are recommended instead of `let` expressions, to reduce nesting.
;; leq2: cx <= lexp2
[(and (eqv? 0 a) (eqv? 0 d)) (leq (lexp-scale l1 c) (lexp-scale r2 b))]
[else (error 'leq-join "cannot join ~a and ~a by ~a" leq1 leq2 x)])))
[else (raise-arguments-error 'leq-join "cannot join and by" "leq1" leq1 "leq2" leq2 "x" x)])))
Copy link
Contributor

Choose a reason for hiding this comment

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

Well that's not right.

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.

2 participants