Sam Tobin-Hochstadt

Here's what's happening: 0. Writing `...` implies that the rest is a list, whereas `a . b` just takes the `car` and `cdr`. So the first two examples are different...

I agree that the printing/input difference is a bug. And #750 should probably be fixed. However, non-NaN types are basically useless in our experience, and the fact that there's a...

This would definitely be good. Unfortunately, I think making it work would require major changes to how Typed Racket handles polymorphism. The kind system in Typed Racket was poorly designed...

It's not clear to me what the use for this would be. Multiple values are special in a way that lists are not, and thus `(Values Number Number)` isn't a...

There are I think two questions here. One is what one could do with a function `f` that had a type like `(-> Integer (Valuesof Integer))`. I think the only...

I don't think this is the right fix -- it's equivalent to just taking out the `section`.

This seems like it breaks existing code, as evidenced by the PRs for other repositories. That doesn't seem like something we want to do, at least not when the breakage...

This has some conflicts, and also the changes to the type annotations in the tests worry me.

The conflict is a merge conflict, with changes to the files that have happened in the mean time. I would like to not change the tests, except perhaps for more...

I think probably more subtyping relationships could be added, so that those programs type check. However, I don't think it makes sense to think of function arguments as similar to...