different TASTy output with scala2-library-tasty

[bishabosha]

Different tasty output affects the stability of outputs

Compiler version

3.5.1-RC1

Minimized code

// A.scala
import Z.*

object A:
  val a: Option[AOptions] = ???
  val b: Option[BOptions] = ???
  val c: Option[COptions] = ???

// Z.scala

enum Z:
  case AOptions()
  case BOptions()
  case COptions()

Output

the output with -Yprint-tasty is different, depending on if scala2-library-tasty is used. Nothing dangerous, just some SHAREDtype being replaced by an equivalent more verbose type.

you can test in the scala3 project with this sbt setting before a task: set ThisBuild/Build.scala2Library := Build.Scala2LibraryTasty

Expectation

should be identical - I would assume that reading Scala 2 library from tasty should result in the same compiler state as from pickles.