sbt/compile
Guillaume Martres 0993c1c7cc Always invalidate API when return type is a value class
Before this commit, we did not do the invalidation for methods with
multiple parameter list, the comment above `hasValueClassAsReturnType`
said:

  Note: We only inspect the "outermost type" (i.e. no recursion) because
  we don't need to inspect after erasure a function that would, for
  instance, return a function that returns a subtype of AnyVal.

But this is wrong: a method with signature:
  def foo(a: A)(b: B): C
is erased to:
  def foo(a: A, b: B): C
and not, as the comment in the code suggest, to:
  def foo(a: A): B => C
so we do need to inspect the final result type of methods, because they
can be value classes that will be erased to their underlying value.
2016-01-25 02:53:34 +01:00
..
api Clean up ShowApi implicit overload 2016-01-06 13:56:54 -05:00
inc Prefix name hashing debug output with [naha] 2016-01-06 13:56:54 -05:00
integration/src/main/scala/sbt/compiler Replace procedure syntax by explicit Unit annotation 2015-08-04 10:07:38 +02:00
interface Always invalidate API when return type is a value class 2016-01-25 02:53:34 +01:00
ivy/src/main/scala/sbt/compiler Fix deprecation messages 2015-09-04 12:25:59 +02:00
persist Replace procedure syntax by explicit Unit annotation 2015-08-04 10:07:38 +02:00
src Make sbt aware of Dotty 2016-01-03 20:35:29 +01:00
NOTICE - Stuart's improvements to triggered execution 2010-07-05 12:53:37 -04:00