Re: [racket-users] Defeating Racket’s separate compilation guarantee

2019-04-24 Thread WarGrey Gyoudmon Ju
Great article, thanks. I like the logging facility, now I see it is more powerful than I known. On Thu, Apr 25, 2019 at 6:25 AM Gustavo Massaccesi wrote: > We can extract an feature request from the end of the post: > > Make the module that define `set` a cross-phase persistent module, so all

Re: [racket-users] Defeating Racket’s separate compilation guarantee

2019-04-24 Thread Gustavo Massaccesi
We can extract an feature request from the end of the post: Make the module that define `set` a cross-phase persistent module, so all the phases can share the `set`s. Gustavo On Sun, Apr 21, 2019 at 7:41 AM Alexis King wrote: > Hello all, > > I just published a blog post on defeating

Re: [racket-users] Defeating Racket’s separate compilation guarantee

2019-04-21 Thread Ben Greenman
One quick thought: I wasn't sure what to expect after reading the current title. How about changing it to say more about the specific exploit? "A terrible hack to move state across Racket phases" "How to smuggle state across phase boundaries" At least, it would have helped me if "separate

[racket-users] Defeating Racket’s separate compilation guarantee

2019-04-21 Thread Alexis King
Hello all, I just published a blog post on defeating Racket’s separate compilation guarantee. While I don’t imagine such a thing is actually a good idea, I think the path to getting there is interesting anyway, and it touches lots of different parts of the Racket system. For those who are