Hmm. I had classOf[Byte] and java.lang.Byte.TYPE, but I thought it was more clear to say "the class of  x when it is an any and when it's not". I guess maybe I'm wrong.

I agree that the overloads should probably disappear in 2.12 (they can't now due to binary compatibility). That said, they do exist now and I thought it felt silly to throw away type information just to immediately recover it in the match. It would make it that much easier to get rid of the overloads to make them delegate to the Any version, though...