Ben Greenman

So happy I'll never need to rebase this PR atop master again.

Right, those files aren't supposed to run. The harness compiles them & looks at the expanded code. (Except for `type-annotation.rkt`, which is unsupported.) I tried adding compile-omit-paths. Also fixed the...

Note that the `case->` formals must (currently) have a different arity if the type is being used to describe an untyped function: ``` #lang typed/racket/base (require/typed racket/base (values (case-> (->...

Yes this is still an issue on Racket 7.4. The code runs the same and the docs make the same statement about formals and arity.

So, should `b` add protection when providing? In general: `require/typed` imports from a typed module get full contracts.

This file also kills frog. I'm not sure why. If I delete everything after line 332 then frog handles it in 1-3 minutes. [2017-10-11-test.md.txt](https://github.com/greghendershott/frog/files/1374298/2017-10-11-test.md.txt)

> Could you clarify why this only works for cloned packages? I'm not understanding that point. Can't this be inferred from the package name-to-source-URL mapping? Or is that not available...

Related: https://github.com/racket/racket/pull/874

yes, I think that's a must for whatever we end up merging EDIT: sam is right, I was thinking about source links (not editing) when I wrote this comment

The suggested wording looks much better.