Arthur Peters
Arthur Peters
This issue should block on #161.
Looking back at this after some time, I'm not sure I actually think this is a good idea. We should discuss.
I have fixed versions of this that actually also unlock when the expression is killed. However they require Orco. I don't see any reason to try for a fix before...
This is almost certainly not worth it in light of the Orctimizer branch. That will supersede this. I will close this when Orctimizer is merged.
Someone should create an upstream issue for this against cpython. I agree that either fix would be reasonable. I suspect the second option would be easier to get merged. Also...
@insertinterestingnamehere This is something we maybe to talk about and return to the system semantics. (I'm a bit embarrassed I didn't see this issue. I had this weird bad feeling...
I think we might actually already track that. Or at least I thought about doing it. The reason was that I wanted to provide fake stacks for exceptions so that...
I tried to handle this by hooking into thread creation. But I might have done it wrong, or not hooked in deeply enough.
@sestephens73 I'm throwing this at you since you are using VCUs. Just something to think about *after* the paper. Discussion with @rossbach triggered this issue, so I'm tagging you here...
We seem to have stabilized on ACU. The code and docs should be updated to reflect that.