Speed up deployment using combined deploy settings.
Fix for SI-5215 part 2: generate return value when eliding method calls
Merge remote-tracking branches 'jsuereth/2.10.0-milestones' and 'szabolcsberecz/SI-5215' into develop
Eliminating duplication in zero creation.
Added the SYNTHETIC flag for BRIDGE methods. The Eclipse Java compiler complains about duplicate methods otherwise.
Disallow eliding when Nothing is expected
Test for SI-5316

Compiler NPE on 2.9.1 when implicit parameter not found
Test for SI-5171

Running the test produces the following error in 2.9.1:
java.lang.VerifyError: class com.restphone.IsList$ overrides final method canEqual.

Works fine in 2.10.0-M2
Merge remote-tracking branches 'som-snytt/elide-nothing', 'szabolcsberecz/SI-5316' and 'szabolcsberecz/SI-5171' into develop
Merge remote-tracking branch 'soc/SI-5034' into develop
Add 2 benchmarks for Ctries.
Deprecate Refined Build Manager.
It contains bugs that we are no longer planning to work on, sbt is a recommended approach (see integration with scala-ide)
Don't populate the concreteSpecMethod set in presentation compiler runs. This is safe because the presentation 
compiler never runs the tree transformer (where this map is needed). This is a source of serious memory leaks in the IDE, but it wasn't visible before because the IDE didn't run the info transformers far enough. Interestingly, this is not a leak in batch runs: each element of the set is removed when the tree is transformed.

For a nice graph of the effect of this change, see: http://i41.tinypic.com/xe0k7o.jpg
Merge remote-tracking branches 'axel22/feature/benchmarks' and 'hubertp/topic/refinedbm'
More use of perRunCaches.

In SpecializeTypes and beyond.  It is hard for me to say with
confidence what might affect the IDE for the worse, but this is
all intended for the IDE's benefit (if only in terms of insurance)
and hopefully intention matches reality.
Disabled one failing test.

One to go (which doesn't fail for me, which is interesting
because it's a VerifyError.)
Revert recent elidable commits.

On epfl jenkins, elidable.scala fails with:

  [partest] java.lang.VerifyError: (class: Test$, method: main signature: ([Ljava/lang/String;)V) Unable to pop operand off an empty stack
  [partest]
  [partest] 	at Test.main(elidable.scala)

Strangely it is fine for me on OSX with either apple's jvm or openjdk.
Since tests were not running for a while I don't know which of the recent
elidable commits is responsible, so given present time demands all I
can do is revert them all.

  Revert "Fix for SI-5215: scalac crash when @elidable used in trait"

  This reverts commit 5e52ce9a13f12ef159e25ac80c6be2803ec48950.

  Revert "Fix for SI-5215 part 2: generate return value when eliding method calls"

  This reverts commit 61c9b4f01d99a81e15391b270bd1b5a895f65ffd.

  Revert "Eliminating duplication in zero creation."

  This reverts commit fbb7865e137e83660257fdc79d19d29ff39c775b.

  Revert "Disallow eliding when Nothing is expected"

  This reverts commit f26a47c4e8bda2f6c689b4e9b0bb5c64ccf4c699.
Reworked and restored elidable.

Found a better elidable implementation which is robust against other
parts of the compiler doing their things. Calls to elidable methods are
replaced with zero of the same type. Elidable methods themselves remain
in place, but with their body replaced with a zero of the method return
type.

Thus is everything to be found where it is expected to be found, but
nothing will be found where nothing ought to be found. Nothing of course
will never be found.
One last nudge for elidable.

A method with return type Nothing elides into a call to ??? .
It's the role ??? was born for.
Methods to derive new DefDefs.

I guess I'd seen DefDef(mods, name, tparams, vparamss, tpt, rhs)
one too many times and went a little crazy.  What do you prefer:

  - val DefDef(mods, name, tparams, vparamss, tpt, rhs) = tree1
  - treeCopy.DefDef(tree1, mods, name, tparams, vparamss, tpt, transform(rhs))
  + deriveDefDef(tree1)(transform)

Me too.