[racket] Unsafe version of require/typed?

From: Eric Dong (yd2dong at uwaterloo.ca)
Date: Fri Mar 20 15:20:38 EDT 2015

It would be nice if we could have an unsafe version of require/typed, which
doesn't generate a contract, but simply "lies" to the type system about the
type. This, of course, breaks the type system's guarantees, and causes UB
if optimizations are one, but in some cases contracts cannot be generated
(for example, for the "object-name" function), but one can create a safe
type for it.

Why can't there be a "require/typed/unsafe" form? It could save a lot of
unnecessary asserts and casts, and unnecessary contract overhead.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20150320/ae1ed928/attachment.html>

Posted on the users mailing list.