@spdegabrielle yes, but you can also go to “Racket > Limit Memory…” and choose “Unlimited”.

If I use make-temporary-file and delete the file, will it be possible for a subsequent make-temporary-file to create the same file name again?

Asking this because in my work, I use dynamic-require on the temporary files, and dynamic-require doesn’t reinstantiate already instantiated modules. I know I can create a new namespace blah blah but I’m too lazy…

https://docs.racket-lang.org/reference/interactive.html?q=dynamic-rere#%28def._%28%28lib._racket%2Frerequire..rkt%29._dynamic-rerequire%29%29

?

“laziness leads to resource optimization, resource optimization leads to efficiency, efficiency leads to loving laziness.”

It’s at least unlikely, since [ms (inexact->exact (truncate (current-inexact-milliseconds)))] is used to generate the filename.

https://github.com/racket/racket/blob/master/racket/collects/racket/file.rkt#L195

Hey @ryanc your crypto package is awesome and I’m loving working with it. I’m just updating my old SSH implementation to the latest syndicate and moving from planet vyzo/crypto to your library in the process.

Thanks for replying! I developed a complicated theory of how/why an exception wasn’t being displayed. In fact? My own wrong use of with-handlers instead of call-with-exception-handler was discarding the exception. :sadpanda:

This was a classic case of, “If it takes 3 days of debugging, it will turn out to be something relatively simple”.

Is there a difference between -call-with-limits on a code - running code in another thread + sync/timeout + kill the thread afterward assuming that there’s no memory restriction?