![]() Since these promises re-evaluate their bodies every time they are forced, allowing them makes `force` not idempotent and not safe to treat as a path. This change is slightly backwards-incompatible, since programs that previously passed `delay/name` promises across the typed boundary will now fail at runtime. The alternative is also incompatible: stop treating `force` as a path. Since `delay/name` is quite obscure, this approach seems like the safer choice. |
||
---|---|---|
.. | ||
typed | ||
typed-racket | ||
unstable | ||
info.rkt | ||
LICENSE.txt |