Separate run time environments

[viebel]

Subsequent calls to stopifyLocally should not interfere each other:

aa = stopify.stopifyLocally(`(() => {
  var sum = 0
  while(true) {
    sum++;
    if(sum % 1e8 === 0) {
      console.info("y:" + sum);
    }
  }
})()`); aa.run(x=>x)

aa = stopify.stopifyLocally(`(() => {
  var sum = 0
  while(true) {
    sum++;
    if(sum % 1e8 === 0) {
      console.info("x:" + sum);
    }
  }
})()`); aa.run(x=>x)

Expected behaviour: print both “x:…” and “y:…”
Actual behaviour: print only “x:…”

@rachitnigam do you think it's a regression?

[arjunguha]

I'm finally back. I don't think this is a regression. We have never tried to do what you're doing.

I think part of the problem is that there is a single global variable that tracks the (single) runtime system instance:

https://github.com/plasma-umass/Stopify/blob/160af366e0fbffed8a9563c585209c7f0c6ef30a/stopify/src/entrypoints/compiler.ts#L25

Frankly, this is just bad design. There may be other issues too. We're happy to work on this.

@sp1tz this could be something to look at

[rachitnigam]

Okay, thanks! I did a brief hack to turn all instances of the runner to use a let instead of var, but that didn't seem to help.

This is a blocker for viebel/klipse#314 (Stopify support for Klipse) so let me know if there a branch with a hacky fix for me to look at.

[arjunguha]

That won't help. It's a genuine global variable. Look at the code that Stopify generates. It assumes a single global variable, I think $S and this is it.

[rachitnigam]

Quick ping to see if there is anything for this. If there is a design doc with an outline for what needs to be done, I can try to hack it up.

[arjunguha]

Nope, go for it! It would be great to have this in.