Sam Tobin-Hochstadt

You can see the relevant types here: https://github.com/racket/typed-racket/blob/0236151e3b95d6d39276353cb5005197843e16e4/typed-racket-lib/typed-racket/base-env/base-env-numeric.rkt#L1961-L2007

The `#` suggests that we're causing memory unsafety, so DrRacket crashing is Typed Racket's fault.

I also get `#` in the error on my HEAD linux version, with CS, so this bug is definitely real.

Ok, I think this is a simple miscommunication between the modules. `a` thinks that it's providing `f` to a typed module, so it doesn't need a contract. `b` thinks that...

@bennn Yes, I agree (basically we should just make `require/typed` not be a typed context).

I think that http://pyret.org uses Frog in this fashion.

I think this was closed unintentionally.

@willghatch usually you can test this by compiling to zo on a few different machines (or with `-j` options to `raco make`) and seeing if you get the same contents.

Both gensym and hash traversal order are affected by what order things happen in globally (for example, memory addresses or how many gensyms have been created). So lots of things...

Looking at the expansion of a simple rash module, here are a few things that might be an issue. 1. It looks like there's an options hash that gets put...