Alex Knauth

I have an idea for checking the problems that lead to warnings: Track ellipsis depth, and when merging pattern-variables together into non-linear patterns, only accept them when the ellipsis-depth of...

While working on #4304 I found that just erroring when nonlinear patterns are detected via the `seen` list, is not enough to catch many nonlinear patterns that should be errors....

It definitely shouldn't be the _default_ method of commenting. There are situations where it would be useful, so as a separate form of comment it may be worth it.

Using `def` for `define` is fine, it's common in other languages and there's no ambiguity. I disagree on `defs` for `define-values` simply because I've often defined `defs` as `(defs (x...

> Please do not fix the problem of "name is too long" with "....so I'll abbreviate parts of it!" After someone mentally expands the abbreviation, they're left with a name...

Another thing worth looking at is the [Parinfer][parinfer] editor extension, and its line invariant for converting between indentation and paren structure in both directions. [parinfer]: https://shaunlebron.github.io/parinfer/

The [`build-source-location`](https://docs.racket-lang.org/syntax/Source_Locations.html#%28def._%28%28lib._syntax%2Fsrcloc..rkt%29._build-source-location%29%29) function from `syntax/srcloc` can act as a `syntax->srcloc` function if you give it a syntax object, although since it can convert from any srcloc representation, perhaps just `->srcloc`...

I love hygiene but I don't think we should be dogmatic about forcing every macro to be hygienic. We should allow unhygienic macros as long as macro implementer goes out...

I think `(min 1.0 1)` and `(min 1 1.0)` should both return `1.0`, an inexact number. It should go like this: ```racket (min x y) case 1, x < y:...

Would the [racket/scribble](https://github.com/racket/scribble) repository be the right place to put this feature request?