1
votes

I just noticed that implicit def doesn't seem to work in var args.

For example, I have a java function that takes java.lang.Byte... as its parameter input. The function call is surround by a scala method that takes scala.Byte.

  implicit def convertTest(bytes: Byte*): Seq[java.lang.Byte] = bytes.map(b => b : java.lang.Byte)

  def test(data: Byte*): Unit ={
    test2(convertTest(data: _*): _*)
  }

  def test2(data: java.lang.Byte*) = {

  }

For some reason I have to explicitly type convertTest() for this to work.

So I tried something without the varargs parameter and found that indeed if I do this, it works:

  implicit def convertTest(bytes: List[Byte]): java.util.List[java.lang.Byte] = bytes.map(b => b : java.lang.Byte).asJava

  def test(data: List[Byte]): Unit ={
    test2(data)
  }

  def test2(data: java.util.List[java.lang.Byte]) = {

  }

Can someone please explain this to me?

1

1 Answers

1
votes

An implicit conversion with a varargs parameter does not make much sense, since you use a varargs parameter so you don't need to explicitly create a collection when you call the function, but with a implicit conversion function, the function is called for you automatically.

You can define a implicit conversion from a Seq[Byte] to a Seq[java.lang.Byte] (like in your second example) and still use the varargs notation in test and test2 (like in your first example).

implicit def convert(bytes: Seq[Byte]): Seq[java.lang.Byte] =
  bytes.map(b => b : java.lang.Byte)

def test(data: Byte*) = test2(data: _*)
def test2(data: java.lang.Byte*) = data.length

Which can be used as :

scala> test(1.toByte, 2.toByte)
res2: Int = 2

scala> test(1.toByte, 2.toByte, 3.toByte)
res3: Int = 3