2

When defining Slick table projections like this:

def * = (id.?, email, human, langUser, langLearn) <> (User2.tupled, User2.unapply)

I observe that tupled method becomes invisible as soon as I define object User2.

My question is what is going on and how to avoid method hiding by companion objects.

Sudheer Aedama
  • 2,116
  • 2
  • 21
  • 39
Marcin
  • 4,080
  • 1
  • 27
  • 54
  • possible duplicate of [Using .tupled method when companion object is in class](http://stackoverflow.com/questions/22367092/using-tupled-method-when-companion-object-is-in-class) – nemo Mar 25 '14 at 01:43

1 Answers1

4

Duplicate of: Using .tupled method when companion object is in class

Tupled on custom case class companions requires manually extending a function type See: https://issues.scala-lang.org/browse/SI-3664 https://issues.scala-lang.org/browse/SI-4808

Community
  • 1
  • 1
cvogt
  • 11,260
  • 30
  • 46