[hotcodereplace] fails if removing a variable from an inner function/lambda that was previously used

I noticed that hot code replace fails whenever a previously "outer" variable get unused.

While this seems reasonable as the scope changes this can be very disruptive and I wonder if JDT in such case not can simply *retain* the reference and therefore will success in code replace?

Current workaround is to be very careful when removing a reference to a variable and simply keep an empty if or system out so the variable do not gets unused.