Alex Knauth

When `tc-e` gets the type, it doesn't normalize it, and subtyping on unions of boxes doesn't work without normalizing it first. How should I fix this? Do I fix subtyping...

This is a limitation of `match`... and the reason Typed Racket doesn't do better here is because the macro is written to allow the user to fail within a match...

I like hyphens in names, because they are both readable within an identifier, while they are also easily distinguished from spaces. This means if there are words, dashes, and spaces...

Or, what if the "Preferences -> Colors -> Color Schemes" page allowed an option for "use as light-mode color scheme" and "use as dark-mode color scheme". This might be more...

I think the three things were: * infix notation: `a + b` with spaces like Pyret * algebra-style function notation: `function(arg, ...)` * parens for grouping: `(a + b)` where...

Could/should we achieve point (2), algebra-style function notation `function(arg, ...)`, the same way Haskell does with tuples? Make `function expr1 expr2 ...` mean function application of multiple arguments, so naturally...

No, I don’t think auto-currying function application like `((add x) y) z` is a good idea for Racket since Racket has variable-arity functions. `add x y z` should mean the...

They will be able to write `f(x, y, z)` because they will be able to write `f arg` with `arg` as a tuple `(x, y, z)`, if `f` is defined...

Ok for some reason it's running fine but showing an ambiguous binding error when compiled. When I tried this for `afl` it didn't have this problem, so I'm not sure...

Ok, apparently it's running fine in DrRacket but not for `raco test`. I still don't know what's going on, because this worked fine for afl.