Investigating what can be done about our 2000 o...

Investigating what can be done about our 2000 or so closures created
via by-name calls takes me through uncurry with a mop. Sifting through
compiler generated classfiles I am horrified at one example of decadent
closure creation perpetrated by a certain extempore. CompilerCommand
goes from 28 classfiles to 16 and manages to get smaller anyway anyway.
Some people just can't be trusted with closures. No review.

1 files changed, 3 insertions, 6 deletions

diff --git a/src/compiler/scala/tools/nsc/symtab/SymbolTable.scala b/src/compiler/scala/tools/nsc/symtab/SymbolTable.scala
index 918f1b37ba..03166de05d 100644
--- a/src/compiler/scala/tools/nsc/symtab/SymbolTable.scala
+++ b/src/compiler/scala/tools/nsc/symtab/SymbolTable.scala
@@ -90,12 +90,9 @@ abstract class SymbolTable extends reflect.generic.Universe
   final def atPhase[T](ph: Phase)(op: => T): T = {
     // Eugene: insert same thread assertion here
     val current = phase
-    try {
-      phase = ph
-      op
-    } finally {
-      phase = current
-    }
+    phase = ph
+    try op
+    finally phase = current
   }
   final def afterPhase[T](ph: Phase)(op: => T): T =
     atPhase(ph.next)(op)