[racket-dev] safe version of racket/unsafe/ops?

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Tue Sep 28 11:13:23 EDT 2010

You could put all the requires into one file and then re-export
things? (At least for now.) Also, you can end up exporting too much,
ie unsafe-call-with-current-continuation :).

Robby

On Mon, Sep 27, 2010 at 11:20 PM, John Clements
<clements at brinckerhoff.org> wrote:
>
> On Sep 27, 2010, at 8:14 PM, Robby Findler wrote:
>
>> I was thinking of something like this:
>>
>>> (require (prefix-in unsafe- racket/fixnum))
>>> (unsafe-fx+ #f #f)
>> fx+: expects type <fixnum> as 1st argument, given: #f; other arguments were: #f
>
> Right, but there are lots of unsafe-ops (e.g.: unsafe-vector-length); if I'm working on a large file that uses racket/unsafe/ops, I'd like to just toggle it to racket/unsafe/actuallynotunsafeops to get better error messages.
>
> John
>
>


Posted on the dev mailing list.