I'd be interested to know this as well. It sounds like something that isn't possible in Racket, since it's essentially specifying how a module can do its job and that requires a level of introspection that I think is excluded by design.
On Thu, Oct 21, 2021 at 10:37 AM kalime...@gmail.com <kalimehta...@gmail.com> wrote: > I've read about protect-out and current-code-inspector, but I still > cannot understand, how to require a module and forbid it to run protected > modules. > > Something like (require untrusted-foo) (foo-proc) but to forbid foo-proc > to use ffi/unsafe. > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-users/5f10a124-6aeb-4389-8421-92034e93f8a7n%40googlegroups.com > <https://groups.google.com/d/msgid/racket-users/5f10a124-6aeb-4389-8421-92034e93f8a7n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAE8gKoeSCaFwYSQzuqy2QJAxEtffMLbqr4q02_gw76f2JCYDdA%40mail.gmail.com.
