Lambda the Ultimate

Okay, it's not quite the right place for this, but I'm stumped and many of you keep tabs on this kind of stuff.

A long time ago I ran into a paper on something I remember being called "statistical defect detection", wherein some clever people wrote software to record which branches were taken leading up to a crash and used those to determine, statistically, which lines of code were most likely to be responsible.

I can't find it any more. Can anyone else remember it? Maybe you can help me find it?

A located lambda calculus. Ezra Cooper and Philip Wadler. Submitted to ICFP 2008.

Several recent language designs have offered a unified language for programming a distributed system; we call these "location-aware" languages. These languages provide constructs that allow the programmer to control the location (the choice of host, for example) where a piece of code should run, which can be useful for security or performance reasons. On the other hand, a central mantra of web engineering insists that web servers should be "stateless": that no "session state" should be maintained on behalf of individual clients---that is, no state that pertains to the particular point of the interaction at which a client program resides. Thus far, most implementations of unified location-aware languages have ignored this precept, usually keeping a process for each client running on the server, or otherwise storing state information in memory. We show how to implement a location-aware language on top of the stateless-server model.

This paper is technical, and I assume most LtU members will mainly read sections 1, 5 & 6. Figure 5 is definition of the located LC.