Scala案例类背后的内容是什么？(What's behind Scala case classes?)

 我对Scala很新，但我已经使用过case类。 我理解常规类和案例类之间的主要区别如此处总结。 
 
 我甚至不想去掉案例类，但我想知道转换所需的代码是什么，例如： 
 
class Tweet(val user: String, val text: String) {
  override def toString: String =
    "User: " + user + "\n" +
    "Text: " + text + "]"
}
 
 进入完整案例“兼容”类。 我的意思是，我想编写案例类的相同“行为”但不使用case关键字。 这是可能的还是编译器做了一些我无法通过代码（不包括优化）的东西？ 
 
 再一次说清楚我要问的是什么，当我需要一个案例类时，我将总是使用case关键字，但是在生命中，我想知道Scala编译器（在一般意义上）对我有什么作用，用代码术语。 
 
 编辑：另外一个疑问：编译器是否会以某种方式标记我的手工编码类与标准案例类的不同，以便我可以在执行中观察到不同的行为？ 

I'm quite new to Scala but I have already used case classes. I understood what are main differences between a regular class and a case class as summarized here.
 
I do not even think to get rid of case classes, but I would like to know what's the code needed to transform for example, this:
 
class Tweet(val user: String, val text: String) {
  override def toString: String =
    "User: " + user + "\n" +
    "Text: " + text + "]"
}
 
into a full case "compatible" class. I mean, I would like to code the same "behavior" of a case class but without using case keyword. Is this possible or does the compiler do something that I cannot get through code (excluding optimizations)? 
 
Once again to make clear what I'm asking, I will always use case keyword when I need a case class, but once in life time, I would like to know what the Scala compiler (in generic sense) does for me, expressed in code terms.
 
edit: An additional doubt: will the compiler mark somehow differently my hand coded class from an standard case class so that I can observe a different behavior in execution?

原文：https://stackoverflow.com/questions/19756894