You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
This might not be an issue, but I wanted to inform and see if there is any possibilities to avoid such problems.
Referring to this discussion and this issue about Slick, found out that the ScalaTest === is overriding the === from Slick probably due to the implicit precedence change in Scala 3.
The problem was solved if I imported import slick.jdbc.H2Profile.api._ inside the test class, thus overriding ===.
In Scala 2, it works without any problem, but in Scala 3 (without -source:3.0-migration) it causes this issue.
Is it possible to avoid the implicit import of === from ScalaTest?
The text was updated successfully, but these errors were encountered:
Hi,
This might not be an issue, but I wanted to inform and see if there is any possibilities to avoid such problems.
Referring to this discussion and this issue about Slick, found out that the ScalaTest
===
is overriding the===
from Slick probably due to the implicit precedence change in Scala 3.The problem was solved if I imported
import slick.jdbc.H2Profile.api._
inside the test class, thus overriding ===.In Scala 2, it works without any problem, but in Scala 3 (without
-source:3.0-migration
) it causes this issue.Is it possible to avoid the implicit import of
===
from ScalaTest?The text was updated successfully, but these errors were encountered: