Open vadzim-marchanka opened 8 months ago
I believe it is expected when you use private
in your case class definition.
Thank you for the response. Should the library behavior be the same for Scala 2 and 3? I expect that people migrating their codebase from Scala 2 to Scala 3 may face this issue.
Ideally, yes it should be the same but I believe this is due to a change of semantic between Scala 2 and 3 for private case class constructors. So Monocle is just following the Scala language.
Hello,
I've noticed that the code that compiles and works fine in scala 2 doesn't work for scala 3.
Scastie: Scala 2 -> https://scastie.scala-lang.org/FmuLKaM0TpmNvQ3xHdpUSg Scala 3 -> https://scastie.scala-lang.org/7FBOxnIPQbemh5TomJrUig
Code:
Error:
Could you please clarify whether it is expected behavior?