any matcher fails to resolve "nested" value classes in 1.7.0

[mikolak-net]

Sorry for being the bearer of bad news, but there appears to be a regression in 1.7.0 . The any matcher (or its underlying macro) is now unable to resolve those stable paths for a value class enclosed in an object that are prefixed with identifier of the same enclosing object.

Test code:

package com.example.test

import org.mockito.{ ArgumentMatchersSugar, IdiomaticMockito }
import org.scalatest.{ FlatSpec, Matchers }

class NestedReproSpec extends FlatSpec with Matchers with IdiomaticMockito with ArgumentMatchersSugar {

  val exampler = mock[Exampler]

  it should "compile a nested value class with direct symbolic reference" in {
    import Nesting.NestedValueClass
    "exampler(any[NestedValueClass]) returns ???" should compile
  }

  it should "compile a nested value class with reference to enclosing object" in {
    "exampler(any[Nesting.NestedValueClass]) returns ???" should compile
  }
}

object Nesting {
  case class NestedValueClass(value: String) extends AnyVal
}

trait Exampler {
  def apply(v: Nesting.NestedValueClass): String
}

Result:

 NestedReproSpec:
 - should compile a nested value class with direct symbolic reference
 - should compile a nested value class with reference to enclosing object *** FAILED ***
   Expected no compiler error, but got the following type error: "not found: value NestedValueClass", for code: exampler(any[Nesting.NestedValueClass]) returns ??? (NestedReproSpec.scala:16)

Not 100% sure if the bug does not affect non-value-classes, but haven't seen such a case yet.

[ultrasecreth]

Wow, thanks for that, 1.7.1 should fix it

Cheers!