News for hackers. Stuff that matters.
Re:Lave: eval in reverse by dspillett on Thursday March 10, 2016 @06:47AM (#11258628)
That would concern me too potentially, though if there isn't one already it should be easy to implement a switch that would turn this part of the behaviour off.

It looks very interesting to me from the point of view of dealing with certain data types better (at all, in fact), and handling circular references.

Re:Lave: eval in reverse by Klathmon on Thursday March 10, 2016 @08:48AM (#11259133)
> it should be easy to implement a switch that would turn this part of the behaviour off

I think it's one of those "easy on the surface, but surprisingly complex" problems.

When you start allowing arbitrary code execution, it's a lot of work to prevent certain "functions" (i mean that in the non-programming way).

Re:Lave: eval in reverse by dspillett on Friday March 11, 2016 @05:12AM (#11265728)
I was thinking more along the lines of turning it off at the generation side: only including anything in the persisted state that is safe.

Trying to detect the unsafe parts so they could be turned off after that point would be impossible as you suspect (the task would be constrained by the halting problem, https://en.wikipedia.org/wiki/Halting_problem).