resyntax
resyntax copied to clipboard
jackfirth
A Racket refactoring engine
`make-temporary-file` with the `'directory` argument used to be the only way to create a temporary directory. However, we now have `make-temporary-directory`, which is the preferred way to create a temporary...
Just like the `for-each` => `for` conversion, some `map`s should be converted to `for/list`. They can use the same heuristics to detect whether they should be converted (i.e. having a...
This one may be difficult, but might be worth trying. Previously, `for/fold` doesn't support `#:result`, so the code could look like this: ``` (define (my-fun) ..... (define-values (a b) (for/fold...
Rewrites ``` (for (....) (when ... .....)) ``` to ``` (for (.... #:when ...) ....) ```
The `--package` option uses `pkg-directory`, which returns `#f` when no such package is installed. In turn, this triggers a contract violation from `simple-form-path`. For example, ``` $ resyntax analyze --package...
See racket/racket#4074. Resyntax could suggest replacing `(read-line in)` with `(read-line in 'any)` and `(read-line)` with `(read-line (current-input-port) 'any)`. This technically changes behavior; a behavior-preserving transformation would be to use `'linefeed`...
Resyntax currently rewrites `(-> any/c boolean?)` to `predicate/c`. This was based on my understanding that `predicate/c` offers improved performance over `(-> any/c boolean?)` for struct predicates. But that's not the...
An easy to overlook error is when folks write `define` in a class body to define a function, using per-instance storage instead of per-class storage. It would be great if...
In https://github.com/racket/drracket/pull/611, it was suggested that it would be helpful if Resyntax-generated pull requests could better summarize themselves. My ideal approach to this would be for Resyntax to group fixes...