Ben Greenman

Cool, thanks for the mailing list link. But still, I think this is an issue with `check-eq?`because library code should not be raising contract errors.

quick update: my dissertation is in and this pull request is now a top priority I'll work on making the test suite reusable first, then get to working on this...

Right now, Shallow code (transient) exports ids using basically the same renamer strategy as normal Deep code. If a Shallow export appears in Shallow or untyped code, it expands to...

The change I'm wondering about wouldn't affect programmers. Deep modules get to use `(require typed.rkt)` no matter what variant of `typed/racket` that file decides to use.

Ah, okay. Right now, Deep doesn't know where imports come from and treats them all uniformly. Deep should know because those contracts are Deep's business, to protect itself. The current...

The [latest test failure](https://github.com/racket/typed-racket/pull/948/checks?check_run_id=3889870480) is on CS only, and seems to be a regression https://github.com/racket/racket/issues/4030 EDIT: issue closed

@samth @capfredf (and anyone else!) the tests are passing & I don't have any other changes planned. Please look this over & send comments and questions. Major highlights: - In...

ping @samth @capfredf , time to merge? ps Jack, resyntax seems to work fine on this PR!

Thanks @capfredf ! I left a few clarifying comments. For everything else, the response is basically: yes and I'll make a change. (no-check is not exactly the same behavior as...

Awesome. I'll add the alias `make-unsafe-shallow-pred-ty` and merge once the tests pass.