Alex Knauth

On the issue, let-to-define tricky case, https://github.com/jackfirth/resyntax/issues/148#issuecomment-893946390 shows a `g` function that gets incorrectly refactored. However, a much simpler version of `g` that also fails in the same way is...

I have an idea to fix this let-to-define tricky case which I hope will fix both the simple `define` and obfuscated macro-generated `define` versions of `g`. My first thought involves...

Roadblock for my idea to fix the let-to-define tricky case: The 2 sets of scopes I would need are not "outside the let" and "inside the let". Instead I need...

I added my solution using `letX-renames` to my PR here: https://github.com/jackfirth/resyntax/pull/166 with these new tests both passing: ```racket test: "let binding with conflicting define inside" ------------------------------ (define (g) (let ([x...

Is there a reason why not?

Are the variations in spaces vs. no spaces from those standards?

The HTML/CSS color names include some alternative spellings, like both `"gray"` and `"grey"`: https://www.w3schools.com/colors/colors_names.asp

Okay. It does make more sense to remove spaces from names before looking them up in the hash table, rather than have multiple copies of an entry in the hash...

I have made https://github.com/racket/draw/pull/17, which just normalizes the spaces. I'm thinking of rebasing and modifying this pull request to only deal with adding `{gray, grey}` to every version of gray,...

> consensus is to make no observable changes to the color names Are you referring to #17 changing the behavior of `"cadet blue"` and `"cornflower blue"` to match the no-space...